知识卡片
供应商不应成为架构核心
把供应商产品视作一个可替换的集成点,以防腐层约束其影响,可以保留业务与技术选项。若围绕它组织全部流程,平台限制会支配未来决策,定制也可能无法补齐差异。沉没投入不应迫使企业把不完整交付宣布为成功。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Evolutionary Architecture Pitfalls and Antipatterns · 查看原书依据
To escape this antipattern, treat all software as just another integration point, even if it initially has broad responsibilities. By assuming integration at the outset, developers can more easily replace behavior that isn’t useful with other integration points, dethroning the king.
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第08章《Evolutionary Architecture Pitfalls and Antipatterns》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch08.html;段落定位:treat all software as just another integration point)
- 结论依据:原文对“供应商不应成为架构核心”的定义或案例,支撑“把供应商产品视作一个可替换的集成点,以防腐层约束其影响,可以保留业务与技术选项”的归纳。据其上下文,若围绕它组织全部流程,平台限制会支配未来决策,定制也可能无法补齐差异。
- 原始内容:To escape this antipattern, treat all software as just another integration point, even if it initially has broad responsibilities. By assuming integration at the outset, developers can more easily replace behavior that isn’t useful with other integration points, dethroning the king.