知识卡片
整体发布不等于必须停机
单体通常以完整工件发布,各团队因此共享一次上线窗口;但完整发布本身不必然造成停机。多个运行实例配合滚动或蓝绿部署可以缓解切换时的可用性风险。真正难点还包括模块之间的隐藏依赖与故障传播,不能把部署粒度和停机结果直接画等号。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第1章《What’s Wrong with Monoliths?》(源文件:`_epub-src/OPS/ch01.xhtml`,归一化正文 [24977:29196))
- 结论依据:原文说明单体通常整体部署、团队共享部署事件,同时指出单体有时可避免停机,并以多实例下的滚动和蓝绿部署作例子。
- 原始内容:Having to deploy a software element as a complete element is not inherently a bad thing. You want to avoid downtime and the resulting lack of application availability. Downtime is sometimes avoidable for classical monoliths, especially backend services. To support high availability, typically, there are multiple instances of a service spread across physical infrastructure, such as in Amazon Web Services (AWS) use of Availability Zones (AZ), by deploying one instance per zone.