知识卡片

普通读书笔记卡 · 5407.a.1

可用场景同时约束降级

理解等级:中级

可用性场景要明确内外部故障来源、遗漏或崩溃等刺激、受影响处理器或存储、正常或维修过载等环境,以及预防、检测、通知、恢复和降级响应。度量可包括检测时间、修复时间、可降级时长和可容忍故障率。服务器故障后无停机继续服务是一个具体目标,不能把所有故障都默认为同一响应。

相关:[[可用性度量依赖服务窗口]]。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 可用性 · 查看原书依据

      Table 4.2 Availability General Scenario An example concrete availability scenario derived from the general scenario in Table 4.2 is shown in Figure 4.1. The scenario is this: A server in a server farm fails during normal operation, and the system informs the operator and continues to operate with no downtime.

    参考来源

    - 位置:《Software Architecture in Practice, 4th Edition》第4章《可用性》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch04.html) - 结论依据:原文的定义、机制或比较支持“可用性场景要明确内外部故障来源、遗漏或崩溃等刺激、受影响处理器或存储、正常或维修过载等环境,以及预防、检测、通知、恢复和降级响应”;正文保留其条件与取舍。 - 原始内容:Table 4.2 Availability General Scenario An example concrete availability scenario derived from the general scenario in Table 4.2 is shown in Figure 4.1. The scenario is this: A server in a server farm fails during normal operation, and the system informs the operator and continues to operate with no downtime.