知识卡片
分布式单体的联动变更
若一个服务每次改动都迫使另一个服务同步修改,服务间可能存在过度耦合:契约缺少抗变更能力,或职责本就应合并。把这样的组件部署成多个进程,仍可能形成分布式单体,承受分布式运行成本却得不到独立变更收益。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Microservice APIs》第 1 章《What are microservice APIs?》(源文件:_epub-src/OEBPS/Text/01.htm)
- 结论依据:1.3.1 节用跨服务联动修改识别不合理耦合,并说明两种可能原因;随后称划分失败会形成同时承受单体与微服务问题的分布式单体。
- 原始内容:In such situations, either the contract between services is not resilient, or there are enough dependencies between both components to justify merging them. Failing to break down a system into independent microservices can result in what Chris Richardson , author of Microservices Patterns , calls a distributed monolith , a situation where you combine all the problems of monolithic architectures with all the problems of microservices, without enjoying the benefits of any of them.