知识卡片
隔离支撑团队并行交付
多团队并行开发和频繁部署,需要让一个团队的变更尽量不迫使其他团队同步修改、验证或等待。隔离提供这种安全边界,既包括代码依赖,也包括发布和故障影响。仅把系统拆成多个部署工件,若仍有隐藏耦合,并不能获得真正的并行交付能力。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第1章《What’s Wrong with Monoliths?》(源文件:`_epub-src/OPS/ch01.xhtml`,归一化正文 [24977:29196))
- 结论依据:原文把多团队并行、同时部署大量变更的安全性与隔离联系起来,并指出高耦合会促成隔离不足。
- 原始内容:Isolation is key to being able to move quickly. If you want multiple teams developing in parallel, if you want safety when deploying hundreds of changes at the same time, you need isolation. Isolation is key to safety, speed, and everything the business and technology want. While high coupling is one form in which monoliths can encourage a lack of isolation, there are many more;