← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 2274.h.7.a.1

聚合不等于服务

理解等级:中级

聚合是必须保持业务不变量的最小强一致单元,不应继续物理拆开,但也不自动值得单独部署。还要看它是否与其他聚合频繁通信、共享值对象及共同变更;联系越强,独立后接口越浅。单聚合服务可能适合特殊需求,通常却会提高全局集成复杂度。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 微服务 · 查看原书依据

      The aggregate’s boundary is the narrowest boundary possible. Decomposing an aggregate into multiple physical services, or bounded contexts, is not only suboptimal but, as you will learn in Appendix A, leads to undesired consequences, to say the least. As bounded contexts, aggregates’ boundaries are also often considered to drive the boundaries of microservices. An aggregate

    参考来源

    - 位置:《Learning Domain-Driven Design》第14章《微服务》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch14.html) - 结论依据:原文以通信、共享值对象、共同变化三个问题说明单聚合服务需要额外判断。 - 原始内容:The aggregate’s boundary is the narrowest boundary possible. Decomposing an aggregate into multiple physical services, or bounded contexts, is not only suboptimal but, as you will learn in Appendix A, leads to undesired consequences, to say the least. As bounded contexts, aggregates’ boundaries are also often considered to drive the boundaries of microservices. An aggregate