知识卡片
金丝雀验证扩容
把扩容方案先开放给少量用户,观察客观性能与伸缩结果,再逐步增加流量,可以评估临时方案的承载边界。它同时是发布控制和验证机制;通过一轮低流量测试不代表高峰必然安全,应明确增加流量的判据及停止条件。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 金丝雀验证扩容
原书出处 · 1 处
- Automating Architectural Governance · 查看原书依据
For the fitness function shown in Figure 4-16, the team initially released the auto-scaling instances to a small group, then increased the number of users as their monitoring showed continued good performance and support.
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第04章《Automating Architectural Governance》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch04.html;段落定位:For the fitness function shown in Figure 4-16)
- 结论依据:原文对“金丝雀验证扩容”的定义或案例,支撑“把扩容方案先开放给少量用户,观察客观性能与伸缩结果,再逐步增加流量,可以评估临时方案的承载边界”的归纳。据其上下文,它同时是发布控制和验证机制;通过一轮低流量测试不代表高峰必然安全,应明确增加流量的判据及停止条件。
- 原始内容:For the fitness function shown in Figure 4-16, the team initially released the auto-scaling instances to a small group, then increased the number of users as their monitoring showed continued good performance and support.