知识卡片
拆分缩小停机协调
共享运行资源越多,升级需要协调的工作负载和团队越多,补丁因此容易长期拖延。把基础设施拆为可独立交付的组件,并为不同应用部署分开的运行实例,可按较小范围安排维护窗口。代价是更多实例和关系管理;复用同一部署定义仍能减少代码差异。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 基础设施代码设计原则 · 查看原书依据
The difficulty of scheduling changes to infrastructure grows (often exponentially) with the number of workloads running on it. More workloads leads to more development teams, more operations teams, and more customer teams that need to agree on a good time to make a change. The difficulty of scheduling infrastructure updates is one of the most
参考来源
- 位置:《Infrastructure As Code》第5章《基础设施代码设计原则》(来源项目 book-sources,源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch05.html)
- 结论依据:原文对该概念的定义、应用条件与作用机制直接支持上述解释。
- 原始内容:The difficulty of scheduling changes to infrastructure grows (often exponentially) with the number of workloads running on it. More workloads leads to more development teams, more operations teams, and more customer teams that need to agree on a good time to make a change. The difficulty of scheduling infrastructure updates is one of the most