返回主题:构件化设计与组装

知识卡片

普通读书笔记卡 · 2313.e.5.o.1

提取领域服务分离部署

理解等级:高级

领域服务把同一业务领域的多个组件提取到独立工程并单独部署,界面改用远程方式访问。最简单形态仍共享数据库,先获取粗粒度部署隔离,再根据各领域实际需求决定微服务细化。过早细化会同时引入数据分解、工作流、分布式事务和运维自动化等成本。

相关:[[领域分组先于服务提取]]。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 基于组件的分解模式 · 查看原书依据

      Too many teams make the mistake of starting out too fine-grained, and as a result must embrace all of the trappings of microservices (such as data decomposition, distributed workflows, distributed transactions, operational automation, containerization, and so on) without the need for all of those fine-grained microservices.

    参考来源

    - 位置:《Software Architecture: The Hard Parts》第5章《基于组件的分解模式》(来源项目: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/ch05.xhtml) - 结论依据:原文的定义、比较或案例支持“领域服务把同一业务领域的多个组件提取到独立工程并单独部署,界面改用远程方式访问”;正文据此解释其用途与适用边界。 - 原始内容:Too many teams make the mistake of starting out too fine-grained, and as a result must embrace all of the trappings of microservices (such as data decomposition, distributed workflows, distributed transactions, operational automation, containerization, and so on) without the need for all of those fine-grained microservices.