知识卡片
服务拆分先大后小
迁移单体时先识别业务功能、事务和部署目标,拆成少量较大服务,再修复集成点并迭代细分。过粗减少不了变化范围,过细会增加通信和协调。渐进粒度让团队在新信息出现时调整,而不是一次承诺难以回退的最终拓扑。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 服务拆分先大后小
原书出处 · 1 处
- Building Evolvable Architectures · 查看原书依据
When migrating an application from a monolithic application architecture to a more services-based one, the architect must pay close attention to how modules are connected in the existing application. Naïve partitioning introduces serious performance problems. The connection points in the application become integration architecture connections, with the attendant latency, availability, and other concerns. Rather than tackle the entire migration at once, a more pragmatic approach
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第07章《Building Evolvable Architectures》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch07.html;段落定位:First, break the monolith into a few large)
- 结论依据:原文对“服务拆分先大后小”的定义或案例,支撑“迁移单体时先识别业务功能、事务和部署目标,拆成少量较大服务,再修复集成点并迭代细分”的归纳。据其上下文,过粗减少不了变化范围,过细会增加通信和协调。
- 原始内容:When migrating an application from a monolithic application architecture to a more services-based one, the architect must pay close attention to how modules are connected in the existing application. Naïve partitioning introduces serious performance problems. The connection points in the application become integration architecture connections, with the attendant latency, availability, and other concerns. Rather than tackle the entire migration at once, a more pragmatic approach