知识卡片
细拆会扩大集成面
把每个业务方法独立成服务看似缩小接口,但这些服务仍需协同、同步状态,于是必须补入大量内部集成接口。单服务变简单而整个系统更复杂,说明不能用最少方法或最小代码作为拆分目标。应同时计算组件自身复杂度和相互依赖的全局复杂度。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 第14章 微服务
原书出处 · 1 处
- 微服务 · 查看原书依据
First, it’s simply not possible. Since the services have to work together, we were forced to expand their public interfaces with integration-related public methods. Second, we won the battle but lost the war. Each service ended up being much simpler than the original design, however the resultant system became orders of magnitude more complex. The
参考来源
- 位置:《Learning Domain-Driven Design》第14章《微服务》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch14.html)
- 结论依据:原文一方法一服务的反例说明局部优化会制造分布式大泥球。
- 原始内容:First, it’s simply not possible. Since the services have to work together, we were forced to expand their public interfaces with integration-related public methods. Second, we won the battle but lost the war. Each service ended up being much simpler than the original design, however the resultant system became orders of magnitude more complex. The