知识卡片
快速恢复依赖可重启设计
快速恢复要求服务可重建状态、启动足够快,并能以任意顺序加入系统。失败后可经负载均衡切换、替换地址,或由客户端查注册表重连;恢复还可能需要重建会话与连接池。有状态数据库通常应使用其成熟复制恢复工具。自动替代实例以后,还须恢复冗余和通知运维,否则系统虽可用却已没有下一层备份。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 构建稳定系统 · 查看原书依据
We need to meet the following conditions to use fast recovery: Services need to be stateless. Startup time of individual services is low (2–3 seconds). Services can start and join the system in any order.
参考来源
- 位置:《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)
- 结论依据:摘录说明快速恢复要求服务可重建状态、启动足够快,并能以任意顺序加入系统。其余条件结合本章相邻例子与取舍说明,数字示例不作当前性能承诺。
- 原始内容:We need to meet the following conditions to use fast recovery: Services need to be stateless. Startup time of individual services is low (2–3 seconds). Services can start and join the system in any order.