知识卡片
横向扩展受状态约束
纵向扩展增加单个实例资源,实施较直接但受机器上限约束;横向扩展增加实例,可获得冗余和更大容量,同时增加协作复杂度。关键在状态:不保存应用状态,或明确地把状态分配给副本,才容易横向扩展。增加机器本身不等于增加有效处理能力。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- What Is a “Cloud Native” Application? · 查看原书依据
A service that doesn’t maintain any application state — or which has been very carefully designed to distribute its state between service replicas — will be relatively straight-forward to scale out. For any other application, it will be hard. It’s that simple. The concepts of scalability, state, and redundancy will be discussed in much more
参考来源
- 位置:《Cloud Native Go》第01章《What Is a “Cloud Native” Application?》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch01.xhtml)
- 结论依据:纵向扩展增加单个实例资源,实施较直接但受机器上限约束;横向扩展增加实例,可获得冗余和更大容量,同时增加协作复杂度。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:A service that doesn’t maintain any application state — or which has been very carefully designed to distribute its state between service replicas — will be relatively straight-forward to scale out. For any other application, it will be hard. It’s that simple. The concepts of scalability, state, and redundancy will be discussed in much more