知识卡片

普通读书笔记卡 · 1237.b.1

切开业务实体会割裂知识

理解等级:高级

CRM的Lead相关规则被应用团队和数据库团队分别实现,两组人又各用一套业务词汇。边界把同一复杂实体的知识切开后,同一规则出现两份表达,修改时立即失去同步,最终污染数据。应检查模型与知识的完整边界,而不只按执行技术或团队资源分配工作;换成另一种存储语言也不会自动修复共享理解缺失。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 附录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.

    参考来源

    - 位置:《Learning Domain-Driven Design》附录A《Applying DDD: A Case Study》(阅读计划17)(来源项目book-sources,源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/app01.html) - 结论依据:原文在所列实例或定义中直接说明本卡讨论的关系;本卡保留相应语境和限制,不把案例结果推广成无条件规则。 - 原始内容: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.