此卡片不在当前主题的阅读序列中,可返回主题继续阅读。
知识卡片
边界与上下文图标明模型适用处
维护多模型完整性,先画清当前地形:Bounded Context 指定每个模型在哪个范围内有效,Context Map 展示这些范围及相互关系。边界之内用持续集成保持术语与规则统一;边界之间再选择共享内核、客户/供应商、遵从、隔离层或各走各路等具体协作方式。
图14.1是这些模式的导航图,不是要求每个项目全部采用。先标注实际边界和依赖,再决定关系策略,才能避免同名概念在不知情时串用。
结构图:
flowchart TD
A[识别各模型实际适用范围] --> B[Bounded Context]
B --> C[Context Map: 标明上下文关系]
B --> D[Continuous Integration: 维持界内统一]
C --> E[选择跨界协作策略]
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Chapter Fourteen. Maintaining Model Integrity · 查看原书依据
A BOUNDED CONTEXT defines the range of applicability of each model, while a CONTEXT MAP gives a global overview of the project's contexts and the relationships between them. This reduction of ambiguity will, in and of itself, change the way things happen on the project, but it isn't necessarily enough. Once we have a CONTEXT BOUNDED, a process of CONTINUOUS INTEGRATION will keep the model unified.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第99章《Chapter Fourteen. Maintaining Model Integrity》(源文件:_epub-src/0321125215_ch14.html;单元02)
- 结论依据:原文定义Bounded Context与Context Map的职责,并说持续集成维护界内统一;图14.1列出关系策略供选择。
- 原始内容:A BOUNDED CONTEXT defines the range of applicability of each model, while a CONTEXT MAP gives a global overview of the project's contexts and the relationships between them. This reduction of ambiguity will, in and of itself, change the way things happen on the project, but it isn't necessarily enough. Once we have a CONTEXT BOUNDED , a process of CONTINUOUS INTEGRATION will keep the model unified.
- 转录说明:末句的 `CONTEXT BOUNDED` 是原 EPUB 的词序笔误,按原样保留;正文按本章反复使用的 `BOUNDED CONTEXT` 理解。