知识卡片
通用子域外购须核算集成与控制
购买或引入开源通用子域实现,可能少写代码、减少自家维护,并获得成熟功能;但要先评估其正确性、稳定性、适配程度和平台依赖。若它过度设计或自带不同模型,集成成本可能超过一个克制的自建实现。
原书同时提到成功采用外部工作流系统和日志包的亲历案例,也说此类方案通常不值得盲目采用。它给的是取舍依据,未声称外购一定优于自建。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第15章|Generic Subdomains · 查看原书依据
I've seen success stories in applications with very elaborate workflow requirements that used commercially available external workflow systems with API hooks.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第119章《Generic Subdomains》(源文件:_epub-src/0321125215_ch15lev1sec3.html;单元02)
- 结论依据:原文逐项列出购买/开源的成熟度与维护收益、质量与集成风险,并给出有成功也有不值得的经验判断。
- 原始内容:Sometimes you can buy an implementation or use open source code. Less code to develop. Maintenance burden externalized. Code is probably more mature, used in multiple places, and therefore more bulletproof and complete than homegrown code. You still have to spend the time to evaluate it and understand it before using it. Quality control being what it is in our industry, you can't count on it being correct and stable. It may be overengineered for your purposes; integration could be more work than a minimalist homegrown implementation. Foreign elements don't usually integrate smoothly. There may be a distinct BOUNDED CONTEXT. [...] It may introduce platform dependencies, compiler version dependencies, and so on. Off-the-shelf subdomain solutions are worth investigating, but they are usually not worth the trouble. I've seen success stories in applications with very elaborate workflow requirements that used commercially available external workflow systems with API hooks. I've also seen success with an error-logging package that was deeply integrated into the application.
- 转录说明:原 EPUB 的列表项在纯文本抽取时重复,此处每项只转录一次;`[...]` 标明外来模型集成风险与平台依赖之间略去的句子。