知识卡片
服务化可作迁移台阶
从单体先到粗粒度领域服务,可以先解决领域和功能分区,再决定哪些领域值得细化成微服务。此阶段通常可保留数据库,继续使用原部署产物,也不强制容器化。它减少一次迁移同时解决的问题,也可成为最终架构;不意味着跨服务的数据与发布耦合已经消失。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 选择架构分解方法 · 查看原书依据
As a stepping-stone, it allows an architect to determine which domains require further levels of granularity into microservices and which ones can remain as coarse-grained domain services (this decision is discussed in detail in Chapter 7).
参考来源
- 位置:《Software Architecture: The Hard Parts》第4章《选择架构分解方法》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch04.xhtml)
- 结论依据:原文的定义、比较或案例支持“从单体先到粗粒度领域服务,可以先解决领域和功能分区,再决定哪些领域值得细化成微服务”;正文据此解释其用途与适用边界。
- 原始内容:As a stepping-stone, it allows an architect to determine which domains require further levels of granularity into microservices and which ones can remain as coarse-grained domain services (this decision is discussed in detail in Chapter 7).