知识卡片
没有运行时依赖可分开建模
两个功能即使出现在同一个用户流程,也不一定需要系统级集成。若它们不调用彼此能力、运行中不共享对象或数据,就可以划成没有连接的限界上下文,各自采用简单的专门模型与技术。
用户仍可在菜单或界面层看到统一入口,但领域逻辑不共享,数据转换尽量少。选择前应确认实际依赖,而非只凭业务主题相近就建立共享模型和翻译层。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第14章|Separate Ways · 查看原书依据
In many circumstances, integration provides no significant benefit. If two functional parts do not call upon each other's functionality, or require interactions between objects that are touched by both, or share data during their operations, then integration, even through a translation layer, may not be necessary. Just because features are related in a use case does not mean they must be integrated.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第110章《Separate Ways》(源文件:_epub-src/0321125215_ch14lev1sec9.html;单元01)
- 结论依据:原文以能力调用、共享对象交互和运行时数据共享判断集成是否必要,并允许界面组织。
- 原始内容:In many circumstances, integration provides no significant benefit. If two functional parts do not call upon each other's functionality, or require interactions between objects that are touched by both, or share data during their operations, then integration, even through a translation layer, may not be necessary. Just because features are related in a use case does not mean they must be integrated.