知识卡片
不同上下文可用不同结构但需顾及统一词汇
每个限界上下文都有自己的命名空间,内部可选择不同大型结构,整体上下文映射也可再用一种结构组织。因此无需强迫相邻上下文采用完全相同的内部模型。
但若每处都选不同结构,项目会失去共同概念的协调价值;统一词汇只是共同概念的一种表达。由此可推:决定局部差异时,应检查整体结构是否仍能帮助团队描述跨上下文职责和关系。这是应用建议,不是原书给出的检查步骤。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第17章|Combining Large-Scale Structures and B OUNDED C ONTEXTS · 查看原书依据
Of course, because each BOUNDED CONTEXT is its own name space, one structure could be used to organize the model within one CONTEXT, while another was used in a neighboring CONTEXT, and still another organized the CONTEXT MAP. However, going too far down that path can erode the value of the large-scale structure as a unifying set of concepts for the project.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第136章《Combining Large-Scale Structures and Bounded Contexts》(源文件:_epub-src/0321125215_ch17lev1sec1.html;单元01)
- 结论依据:原文允许不同上下文和上下文映射使用不同结构,同时提醒过度分化会削弱统一概念。
- 原始内容:Of course, because each BOUNDED CONTEXT is its own name space, one structure could be used to organize the model within one CONTEXT , while another was used in a neighboring CONTEXT , and still another organized the CONTEXT MAP . However, going too far down that path can erode the value of the large-scale structure as a unifying set of concepts for the project.