知识卡片
内部团队结构影响上下文关系
在团队自己控制的系统内,高关联功能与较小团队可以共用一个上下文;团队扩大后若持续集成困难,可拆分相对独立的功能,用[[共享内核只共享双方必需的模型子集]]维护必要交集。依赖单向时可考虑客户/供应商团队;两组人的模型持续冲突且原因难消除时,可分开模型、共同维护翻译接口。
原书说“少于十人”是示例性经验,不是固定人数上限;一队可管多个上下文,多队共管一个通常较难。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第14章|Choosing Your Model Context Strategy · 查看原书依据
As the team grows larger, CONTINUOUS INTEGRATION may become difficult (although I have seen it maintained for somewhat larger teams). You may look for a SHARED KERNEL and break off relatively independent sets of functionality into separate BOUNDED CONTEXTS, each with fewer than ten people. If all of the dependencies between two of these go in one direction, you could set up CUSTOMER/SUPPLIER DEVELOPMENT TEAMS.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第114章《Choosing Your Model Context Strategy》(源文件:_epub-src/0321125215_ch14lev1sec13.html;单元03)
- 结论依据:原文讨论团队规模、持续集成、共享内核、单向依赖与团队思维冲突对应的不同边界策略。
- 原始内容:As the team grows larger, CONTINUOUS INTEGRATION may become difficult (although I have seen it maintained for somewhat larger teams). You may look for a SHARED KERNEL and break off relatively independent sets of functionality into separate BOUNDED CONTEXTS , each with fewer than ten people. If all of the dependencies between two of these go in one direction, you could set up CUSTOMER/SUPPLIER DEVELOPMENT TEAMS .