知识卡片
何时不投资演进能力
严重纠缠系统可能重写比逐步改造更合适;极端领域特征可能优先于演进;验证市场的可抛弃系统或即将结束的业务也未必值得追加投入。应比较收益期限、可行性与机会成本,而不是把可演进性当作无条件义务。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Putting Evolutionary Architecture into Practice · 查看原书依据
We don’t believe that evolutionary architecture is the cure for all ailments! Companies have several legitimate reasons to pass on these ideas. Here are some common reasons. Can’t evolve a Big Ball of Mud One of the key “-ilities” architects neglect is feasibility—should the team undertake this project? If an architecture is a hopelessly coupled Big Ball of Mud, making it possible to evolve it
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第09章《Putting Evolutionary Architecture into Practice》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch09.html;段落定位:Companies have several legitimate reasons)
- 结论依据:原文对“何时不投资演进能力”的定义或案例,支撑“严重纠缠系统可能重写比逐步改造更合适;极端领域特征可能优先于演进;验证市场的可抛弃系统或即将结束的业务也未必值得追加投入”的归纳。据其上下文,应比较收益期限、可行性与机会成本,而不是把可演进性当作无条件义务。
- 原始内容:We don’t believe that evolutionary architecture is the cure for all ailments! Companies have several legitimate reasons to pass on these ideas. Here are some common reasons. Can’t evolve a Big Ball of Mud One of the key “-ilities” architects neglect is feasibility—should the team undertake this project? If an architecture is a hopelessly coupled Big Ball of Mud, making it possible to evolve it