知识卡片
先建立逻辑子域边界
现代化先把命名空间、模块或包按业务子域组织,再选值得付成本的地方转为物理上下文。移动类型通常比改业务安全,但要检查反射和全名动态引用;数据库过程、函数等散布平台上的逻辑也要纳入。多团队需独立交付或冲突模型混在一起,是进一步物理拆分的明确理由。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 现实中的领域驱动设计 · 查看原书依据
A prerequisite for making this decision is to have boundaries dividing the system’s subdomains. The boundaries don’t have to be physical, making each subdomain a full-fledged bounded context. Instead, start by ensuring that at least the logical boundaries (namespace, modules, and packages, depending on the technology stack) are aligned with the subdomains’ boundaries, as shown
参考来源
- 位置:《Learning Domain-Driven Design》第13章《现实中的领域驱动设计》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch13.html)
- 结论依据:原文先要求逻辑边界对齐子域,再按团队生命周期和模型冲突选择物理拆分。
- 原始内容:A prerequisite for making this decision is to have boundaries dividing the system’s subdomains. The boundaries don’t have to be physical, making each subdomain a full-fledged bounded context. Instead, start by ensuring that at least the logical boundaries (namespace, modules, and packages, depending on the technology stack) are aligned with the subdomains’ boundaries, as shown