知识卡片
故障隔离需要断开同步依赖
容错在此指部分系统失败时,其余部分仍可用。拆成独立部署单元能把内存耗尽等灾难故障限制在局部;复制整个单体对所有副本共有的程序缺陷帮助有限。若健康服务同步依赖故障服务,隔离仍会失效;异步通信可减少这种运行依赖,前提是业务允许延后处理。
相关:[[模块化必须回应业务]]。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 架构模块化的业务驱动 · 查看原书依据
By breaking apart the system into multiple deployment units, catastrophic failure is isolated to only that deployment unit, thereby allowing the rest of the system to function normally. There is a caveat to this, however: if other services are synchronously dependent on a service that is failing, fault tolerance is not achieved.
参考来源
- 位置:《Software Architecture: The Hard Parts》第3章《架构模块化的业务驱动》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch03.xhtml)
- 结论依据:原文的定义、比较或案例支持“容错在此指部分系统失败时,其余部分仍可用”;正文据此解释其用途与适用边界。
- 原始内容:By breaking apart the system into multiple deployment units, catastrophic failure is isolated to only that deployment unit, thereby allowing the rest of the system to function normally. There is a caveat to this, however: if other services are synchronously dependent on a service that is failing, fault tolerance is not achieved.