← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 4545.c.7

弹性也要在峰值后缩回

理解等级:中级

峰值时增加实例可保持服务,需求回落后减少实例则避免为闲置容量持续付费。自动化部署和明确的状态边界使扩缩更容易执行。原书飓风事件是这套能力的个案,不能把一次加机器成功推成任意业务都可无风险十倍扩容。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Scalability · 查看原书依据

      Second, having far more resources than necessary isn’t just wasteful, it’s expensive. The ability to scale our instances back in when demand ebbed meant that we were only paying for the resources that we needed. A major plus for a startup on a budget. Unfortunately, because unscalable services can seem to function perfectly well under

    参考来源

    - 位置:《Cloud Native Go》第07章《Scalability》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch07.xhtml) - 结论依据:峰值时增加实例可保持服务,需求回落后减少实例则避免为闲置容量持续付费。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。 - 原始内容:Second, having far more resources than necessary isn’t just wasteful, it’s expensive. The ability to scale our instances back in when demand ebbed meant that we were only paying for the resources that we needed. A major plus for a startup on a budget. Unfortunately, because unscalable services can seem to function perfectly well under