知识卡片
共享内核变更须跨团队协商与测试
共享内核由两个团队共同依赖,变更时应先沟通,合并时运行双方测试并保证都通过。各团队仍可在独立副本上工作,定期集成整个功能系统;跨团队内核合并通常可比团队内部持续集成稍慢,但沟通不应等到合并时才开始。
原书以“团队每日或更频繁集成、内核可能每周合并”作示例,频率依项目节奏选择。共享内核换来较少重复和较易集成,也使内核变更不如各自私有部分自由。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第14章|Shared Kernel · 查看原书依据
Usually, teams make changes on separate copies of the KERNEL, integrating with the other team at intervals. (For example, on a team that CONTINUOUSLY INTEGRATES daily or better, the KERNEL merger might be weekly.) Regardless of when code integration is scheduled, the sooner both teams talk about the changes, the better.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第105章《Shared Kernel》(源文件:_epub-src/0321125215_ch14lev1sec5.html;单元01)
- 结论依据:原文明确跨团队咨询、双方测试、独立副本和间隔集成,以及尽早讨论变更的要求。
- 原始内容:Integrate a functional system frequently, but somewhat less often than the pace of CONTINUOUS INTEGRATION within the teams. At these integrations, run the tests of both teams. It is a careful balance. The SHARED KERNEL cannot be changed as freely as other parts of the design. Decisions involve consultation with another team. Automated test suites must be integrated because all tests of both teams must pass when changes are made. Usually, teams make changes on separate copies of the KERNEL , integrating with the other team at intervals. (For example, on a team that CONTINUOUSLY INTEGRATES daily or better, the KERNEL merger might be weekly.) Regardless of when code integration is scheduled, the sooner both teams talk about the changes, the better. [...] The goal is to reduce duplication (but not to eliminate it, as would be the case if there were just one BOUNDED CONTEXT ) and make integration between the two subsystems relatively easy.