知识卡片
自动扩容需要余量与上限
自动扩缩按负载调整实例数,可减少低谷浪费,但启动和配置并非瞬时完成。应保留应对增长的余量、缩短启动时间,并设合理上限防止异常流量或级联故障无限消耗预算。限流和卸载为扩容争取时间,不能用自动扩容替代容量约束。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Resilience · 查看原书依据
No matter how fast your startup, scaling takes a non-zero amount of time. Your service should have some wiggle room without having to scale. As we discussed in “Scaling Postponed: Efficiency”, the best kind of scaling is the kind that never needs to happen. Healthy Health Checks In “Service Redundancy”, we briefly discussed the value
参考来源
- 位置:《Cloud Native Go》第09章《Resilience》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch09.xhtml)
- 结论依据:自动扩缩按负载调整实例数,可减少低谷浪费,但启动和配置并非瞬时完成。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:No matter how fast your startup, scaling takes a non-zero amount of time. Your service should have some wiggle room without having to scale. As we discussed in “Scaling Postponed: Efficiency”, the best kind of scaling is the kind that never needs to happen. Healthy Health Checks In “Service Redundancy”, we briefly discussed the value