知识卡片

普通读书笔记卡 · 3327.l

迁移可先重聚合再拆分

理解等级:高级

当数百服务之间的依赖已无法可靠分析时,继续增加服务可能扩大迁移风险。可评估先把高度耦合部分整合为有模块边界的单体,恢复可观察、可测试和可重构的范围,再按真实领域边界拆分。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    原书出处

    参考来源

    - 位置:《Principles of Software Architecture Modernization》第3章《Anti-Patterns: Distributed Monoliths》(源文件:`_epub-src/OPS/ch03.xhtml`,归一化正文 [58929:63115)) - 结论依据:原文指出分布式单体比单体更难理解和重构,并在本章止血建议中提出重新聚合为单体的选择;模块边界是实施时的限制。 - 原始内容:Distributed monoliths are much more difficult to fix than monoliths. With monoliths, at least the code base is in one place, and you can use your IDE to delete code and see the impact in seconds. When you have a distributed monolith, understanding the impact of changes and even applying refactoring is much more complex as you do not have all the code in your IDE, and certainly can’t run hundreds of services.