知识卡片
命名约束维持领域边界
领域重构后,用允许的领域名单阻止源码悄悄进入新领域;领域服务提取后,检查其中组件都使用对应命名空间前缀。这只能治理结构归属,不能自动判断业务语义正确,因此名单和领域划分仍需人工协作。持续检查让后续维护不把领域服务重新变成无结构单体。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 基于组件的分解模式 · 查看原书依据
This automated holistic fitness function can be triggered on deployment through a CI/CD pipeline to restrict the domains contained within an application. This fitness function helps prevent additional domains from being inadvertently created by development teams and alerts the architect if any new namespaces (or directories) are created outside the approved list of domains.
参考来源
- 位置:《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)
- 结论依据:原文的定义、比较或案例支持“领域重构后,用允许的领域名单阻止源码悄悄进入新领域;领域服务提取后,检查其中组件都使用对应命名空间前缀”;正文据此解释其用途与适用边界。
- 原始内容:This automated holistic fitness function can be triggered on deployment through a CI/CD pipeline to restrict the domains contained within an application. This fitness function helps prevent additional domains from being inadvertently created by development teams and alerts the architect if any new namespaces (or directories) are created outside the approved list of domains.