知识卡片
外部系统不自动构成限界上下文
遗留系统、外部服务通常先从本系统设计范围中划出,但“一个系统”不必然等于“一个[[限界上下文界定模型一致范围]]”。限界上下文需要有人有意维护边界内模型一致;外部系统内部可能由不同团队松散改动,同一概念在不同模块甚至互相矛盾。
把它接入前应查清维护者、集成习惯与语义一致性,再确定需要翻译哪些概念。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第14章|Choosing Your Model Context Strategy · 查看原书依据
It is convenient to think of each of these systems as constituting its own BOUNDED CONTEXT, but most external systems only weakly meet the definition. First, a BOUNDED CONTEXT is defined by an intention to unify the model within certain boundaries. You may have control of maintenance of the legacy system, in which case you can declare the intention, or the legacy team may be well coordinated and be carrying out an informal form of CONTINUOUS INTEGRATION, but don't take it for granted. Check into it, and if the development is not well integrated, be particularly cautious. It is not unusual to find semantic contradictions in different parts of such systems.