知识卡片
用业务理由推动DDD
DDD可以作为日常工程工具逐步采用,无需先让全组织接受所有术语。倾听领域词汇、澄清同义与异义、在代码和交流中使用统一语言;讨论聚合与边界时解释一致性、认知负担和重复逻辑风险。是否采用事件溯源也应让领域专家比较时间维度带来的价值,再由业务需要驱动决定。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 现实中的领域驱动设计 · 查看原书依据
Make domain-driven design a part of your professional toolbox, not an organizational strategy. DDD’s patterns and practices are engineering techniques, and since software engineering is your job, use them! Let’s see how to incorporate DDD into your day-to-day job without making much ado about it. Ubiquitous language The use of a ubiquitous language is the
参考来源
- 位置:《Learning Domain-Driven Design》第13章《现实中的领域驱动设计》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch13.html)
- 结论依据:原文强调务实、非全有或全无,用逻辑而非权威推广,并让专家评估事件模型收益。
- 原始内容:Make domain-driven design a part of your professional toolbox, not an organizational strategy. DDD’s patterns and practices are engineering techniques, and since software engineering is your job, use them! Let’s see how to incorporate DDD into your day-to-day job without making much ado about it. Ubiquitous language The use of a ubiquitous language is the