知识卡片
专有算法构成差异化价值时可留在核心
通常把求解机制移出核心领域;例外是算法本身构成产品的专有差异化价值。原书举运输排程的假设例,并回忆投资银行项目的实际风险评级算法被视为核心,甚至限制多数核心开发人员访问。
即便如此,算法也可能只是更深风险规则的一种实现。是否再把规则显性建模、机制封装求解,取决于新设计的难度、当前维护成本、预期收益与团队是否已有可行模型,不能把“专有”当成永远拒绝重构的理由。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第15章|Cohesive Mechanisms · 查看原书依据
I once worked on a project at an investment bank in which highly proprietary algorithms for rating risk were definitely in the CORE DOMAIN. (In fact, they were held so closely that even most of the CORE developers were not allowed to see them.) Of course, these algorithms are probably a particular implementation of a set of rules that really predict risk.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第122章《Cohesive Mechanisms》(源文件:_epub-src/0321125215_ch15lev1sec6.html;单元02–03)
- 结论依据:原文提出专有关键算法例外、银行项目经历,并用成本收益问题限定进一步建模。
- 原始内容:You almost always want to remove MECHANISMS from the CORE DOMAIN. The one exception is when a MECHANISM is itself proprietary and a key part of the value of the software. This is sometimes the case with highly specialized algorithms. For example, if one of the distinguishing features of a shipping logistics application were a particularly effective algorithm for working out schedules, that MECHANISM could be considered part of the conceptual CORE. I once worked on a project at an investment bank in which highly proprietary algorithms for rating risk were definitely in the CORE DOMAIN. (In fact, they were held so closely that even most of the CORE developers were not allowed to see them.) Of course, these algorithms are probably a particular implementation of a set of rules that really predict risk. Deeper analysis might lead to a deeper model that would allow those rules to be explicit, with an encapsulated solving mechanism. [...] The decision as to whether to go that next step would be based on a cost-benefit analysis: How difficult would it be to work out that new design? How difficult is the current design to understand and modify? How much easier would it be with a more advanced design, for the type of people who would be expected to do the work? And of course, does anyone have any idea what form the new model might take?
- 转录说明:`[...]` 标明银行案例后的设计过渡句省略;原 EPUB 强调标签边界造成的术语前空格已规范转录。运输排程是作者假设,银行风险评级是作者实际项目。