← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1841.h.1.a.1.a.3.f.1.c

领域边界包住技术层

理解等级:高级

按技术层组织时,一个业务变化会穿过界面、业务和持久层;按领域组织则把相关技术部件集中在服务边界内。后者常使领域变化更局部,但本身也带来分布式协作成本。原书“分层领域演进性为零”是强调跨层协调的修辞,不应照读为所有分层系统都不能演进。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Evolutionary Architecture Topologies · 查看原书依据

      In microservices architecture, the domain encapsulates technical and other architectures, making evolution across domain dimensions easy. No one perspective on architecture is “correct” but rather a reflection of the goals developers build into their projects. If the focus is entirely on technical architecture, then making changes across that dimension is easier. However, if the domain perspective is ignored, then evolving across that dimension is no

    参考来源

    - 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第05章《Evolutionary Architecture Topologies》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch05.html;段落定位:In microservices architecture, the domain encapsulates technical) - 结论依据:原文对“领域边界包住技术层”的定义或案例,支撑“按技术层组织时,一个业务变化会穿过界面、业务和持久层;按领域组织则把相关技术部件集中在服务边界内”的归纳。据其上下文,后者常使领域变化更局部,但本身也带来分布式协作成本。 - 原始内容:In microservices architecture, the domain encapsulates technical and other architectures, making evolution across domain dimensions easy. No one perspective on architecture is “correct” but rather a reflection of the goals developers build into their projects. If the focus is entirely on technical architecture, then making changes across that dimension is easier. However, if the domain perspective is ignored, then evolving across that dimension is no