知识卡片

问题卡 · 4545.a.4.c

拆分早于交付能力

理解等级:中级

服务数量增加而部署、测试和运维仍手工时,协调成本会迫使团队重新统一发布,逐渐形成分布式单体。应先以小范围完整应用建立所需交付、封装、观测及责任能力,再扩服务数;问题在依赖失配,不在微服务数量本身。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Chapter 13. Common Transformation Challenges · 查看原书依据

      When this happens, the result is literally hundreds of mini-monoliths running simultaneously—all of which need to be deployed manually. A nightmare, basically, which is happening because once again a monolithic team structure is expressing itself, via Conway’s Law, as a large number of strong inter-team dependencies. Figure 13-7 does not fully depict the chaos.

    参考来源

    - 位置:《Cloud Native Transformation》第13章《Common Transformation Challenges》(来源项目a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Cloud Native Transformation/_epub-src/OEBPS/ch13.xhtml) - 结论依据:原文描述失败场景、产生失配的原因及相应的模式化改进方向,支持本卡的核心论点:服务数量增加而部署、测试和运维仍手工时,协调成本会迫使团队重新统一发布,逐渐形成分布式单体。本卡进一步说明用途及适用边界;原文过强的保证另在正文限界。 - 原始内容:When this happens, the result is literally hundreds of mini-monoliths running simultaneously—all of which need to be deployed manually. A nightmare, basically, which is happening because once again a monolithic team structure is expressing itself, via Conway’s Law, as a large number of strong inter-team dependencies. Figure 13-7 does not fully depict the chaos.