知识卡片
快速恢复依赖启动设计
快速恢复要求服务启动足够快、能并行启动而非长依赖链,并能取得最新状态。可用懒加载缩短就绪时间,以数据库复制保状态、其余层自动重建。书中2至3秒是目标示例,不是所有容器的保证;恢复还需识别原始故障,资源压力下反复重启可能形成循环。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 高可用与扩展 · 查看原书依据
Services or components need to be able to start concurrently without a specific order. Otherwise, it takes too long to bring up the system. The new system needs to get an up-to-date state from the old system. One common approach is replicating the database but quickly recovering the rest of the system.
参考来源
- 位置:《Software Architecture and Decision-Making》第09章《高可用与扩展》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch09.xhtml)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:Services or components need to be able to start concurrently without a specific order. Otherwise, it takes too long to bring up the system. The new system needs to get an up-to-date state from the old system. One common approach is replicating the database but quickly recovering the rest of the system.