知识卡片
限界上下文限定语言
限界上下文是模型与业务语言保持一致的范围。同为订单,在结账中可以修改,在履约中是不可变指令,在库存中可能指采购单;客户在不同上下文也只暴露相关信息。因此不能以统一企业模型强行抹平差异。一个上下文可由多个服务实现,但一个服务不能跨越多个上下文。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 自治、边界与隔离 · 查看原书依据
DDD advocates for a ubiquitous language shared by different stakeholders, in particular domain experts and software developers. But with DDD the agreement on language, terms, and concepts is valid only within one bounded context, which is contradictory to a lot of enterprise architecture approaches where an attempt is made to define a common language for
参考来源
- 位置:《Practical Process Automation》第7章《自治、边界与隔离》(来源项目:book-sources;源文件:extracted/Practical Process Automation (Bernd Ruecker)/_epub-src/OEBPS/ch07.xhtml)
- 结论依据:原文给出的机制、实例与边界支持本卡的解释。
- 原始内容:DDD advocates for a ubiquitous language shared by different stakeholders, in particular domain experts and software developers. But with DDD the agreement on language, terms, and concepts is valid only within one bounded context, which is contradictory to a lot of enterprise architecture approaches where an attempt is made to define a common language for