原书出处
Learning Domain-Driven Design
17 附录A:应用DDD的案例
This situation produced an implicit bounded context whose boundary dissected one of our most complex business entities: the Lead. The result was two teams working on the same business component and implementing closely related features, but with minimal interaction between them. Ubiquitous language? Give me a break! Literally, each team had its own vocabulary to describe the business domain and its rules. The models were inconsistent. There was no shared understanding. Knowledge was duplicated, and the same rules were implemented twice. Rest assured, when the logic had to change, the implementations went out of sync immediately.
原书定位详情
来源:a19c7933-4eda-4176-aebd-30fe7e1ad292
正文位置:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/app01.html
EPUB SHA-256:da8d47219d6910f6431498e98b9fadfbdadc1cb0e3004bae825392a2c6abc846