知识卡片
混合范式先验证净收益
引入规则引擎等第二范式前,先尝试用现有范式表达目标概念,并确认新工具真正改善表达、足以抵消集成和维护成本。采用后不要强迫模型迎合某种图示工具;可用适合该范式的图或文字说明。跨工具的命名要保持一致,让业务讨论能检验两端是否仍是同一模型。参见[[混合范式须共享同一模型]]。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第05章|Modeling Paradigms · 查看原书依据
Is the tool really pulling its weight? Just because you have some rules, that doesn't necessarily mean you need the overhead of a rules engine. Rules can be expressed as objects, perhaps a little less neatly; multiple paradigms complicate matters enormously.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第42章《原书第05章|Modeling Paradigms》(源文件:_epub-src/0321125215_ch05lev1sec6.html)
- 结论依据:原文列出混合范式的四条经验规则:顺应实现范式、依靠通用语言、不被 UML 限制、质疑工具收益,并要求先穷尽主范式内的方案。
- 原始内容:Don't fight the implementation paradigm . ... Lean on the ubiquitous language . ... Don't get hung up on UML . ... Be skeptical . ... Is the tool really pulling its weight? Just because you have some rules, that doesn't necessarily mean you need the overhead of a rules engine. Rules can be expressed as objects, perhaps a little less neatly; multiple paradigms complicate matters enormously.