知识卡片
早期绑定放大后续改动
分布部署、分层、同步或异步、加密、操作系统和协议等选择会限制大量后续决定。修改其中一个,可能要求依赖它的决定一起调整,形成从涟漪到雪崩的影响。架构不是仅由早期决定定义,但这些难逆绑定尤其值得在投入扩大前审查。
相关:[[变化分局部非局部和架构]]。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 软件架构为何重要 · 查看原书依据
So it is with architecture design. An architecture design can also be viewed as a set of decisions. Changing these early decisions will cause a ripple effect, in terms of the additional decisions that must now be changed. Yes, sometimes the architecture must be refactored or redesigned, but this is not a task we undertake lightly—because the “ripple” might turn into an avalanche.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第2章《软件架构为何重要》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch02.html)
- 结论依据:原文的定义、机制或比较支持“分布部署、分层、同步或异步、加密、操作系统和协议等选择会限制大量后续决定”;正文保留其条件与取舍。
- 原始内容:So it is with architecture design. An architecture design can also be viewed as a set of decisions. Changing these early decisions will cause a ripple effect, in terms of the additional decisions that must now be changed. Yes, sometimes the architecture must be refactored or redesigned, but this is not a task we undertake lightly—because the “ripple” might turn into an avalanche.