知识卡片
恢复路径必须实际演练
恢复分支平时很少运行,可能坏了很久仍没人发现。可用故障演练测试切换、重连和恢复冗余,进阶做法是随机注入故障,迫使系统反复走恢复路径。观测应包括拓扑变化和独立业务吞吐,避免“节点活着”掩盖实际业务停顿。演练验证的是已覆盖场景,不证明系统能处理一切组合。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 构建稳定系统 · 查看原书依据
Furthermore, failures are often rare; thus, recovery paths rarely run. Therefore, if recovery paths are broken, we would not know about that situation until it’s too late. It is a good idea to conduct drills that simulate failures to test the recovery path.
参考来源
- 位置:《Software Architecture and Decision-Making》第12章《Building Stable Systems》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch12.xhtml)
- 结论依据:摘录说明恢复分支平时很少运行,可能坏了很久仍没人发现。其余条件结合本章相邻例子与取舍说明,数字示例不作当前性能承诺。
- 原始内容:Furthermore, failures are often rare; thus, recovery paths rarely run. Therefore, if recovery paths are broken, we would not know about that situation until it’s too late. It is a good idea to conduct drills that simulate failures to test the recovery path.