知识卡片

普通读书笔记卡 · 3439

微服务的运维代价

理解等级:高级

微服务可让组件分别扩容和小批量发布,故障回退范围也可能缩小;同时它增加基础设施开销,使监控、运行与跨服务追踪更复杂。判断是否拆分时,应把交付收益与持续运维成本一起衡量;服务数量增加本身不是架构改进。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    原书出处

    参考来源

    - 位置:《Microservice APIs》第一部分导言与第 1 章《What are microservice APIs?》(源文件:_epub-src/OEBPS/Text/p1.htm、_epub-src/OEBPS/Text/01.htm) - 结论依据:部分导言同时写明独立扩容与发布收益、基础设施和追踪成本;第 1 章 1.1.2 节又说明较小发布便于控制和回退,同时强调微服务不是万能方案。 - 原始内容:microservices allow you to leverage the power of distributed applications, scale components more easily, and release faster. ... They bring a substantial infrastructure overhead, and they’re more difficult to monitor, operate, and trace. ... Consequently, we can make small changes to the code and release more often. Smaller releases are more controllable, and if we spot a bug, the releases are easier to roll back.