知识卡片
隔离核心的代价由关键上下文价值抵偿
隔离核心可能让原本紧密相连的非核心类之间关系更绕,也可能拆散旧模块的局部内聚;改动范围还可能遍及系统,开发投入很大。这些是实际设计代价,不能只看新包结构是否整洁。
原书给出的适用时机是:关键的大型限界上下文中,核心模型被大量支持能力遮蔽,导致核心难以理解和维护。此时优先提高企业特有核心的内聚性,才可能抵偿外围复杂度与迁移成本。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第15章|Segregated Core · 查看原书依据
The SEGREGATED CORE will let you enhance the cohesion of that CORE DOMAIN. There are many meaningful ways of breaking down a model, and sometimes in the creation of a SEGREGATED CORE a nicely cohesive MODULE may be broken, sacrificing that cohesion for the sake of bringing out the cohesiveness of the CORE DOMAIN. This is a net gain, because the greatest value-added of enterprise software comes from the enterprise-specific aspects of the model. The other cost, of course, is that segregating the CORE is a lot of work. It must be acknowledged that a decision to go to a SEGREGATED CORE will potentially absorb developers in changes all over the system. The time to chop out a SEGREGATED CORE is when you have a large BOUNDED CONTEXT that is critical to the system, but where the essential part of the model is being obscured by a great deal of supporting capability.