知识卡片
循环依赖扩散变化
组件形成依赖环后,想复用其中一个组件往往必须带走整个环,修改也更容易传播。IDE自动导入让此类问题容易悄然积累。将无环约束放进持续构建,可以在依赖出现时反馈;治理范围必须具体到适合分析的包或组件集合。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 循环依赖扩散变化
原书出处 · 1 处
- Fitness Functions · 查看原书依据
Architects consider the cyclic dependency shown in Figure 2-2 an antipattern because it presents difficulties when a developer tries to reuse one of the components—each of the entangled components must also come along. Thus, in general, architects want to keep the number of cycles low. However, the universe is actively fighting the architect’s desire to prevent this problem via convenience tools. What happens when a
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第02章《Fitness Functions》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch02.html;段落定位:Architects consider the cyclic dependency)
- 结论依据:原文对“循环依赖扩散变化”的定义或案例,支撑“组件形成依赖环后,想复用其中一个组件往往必须带走整个环,修改也更容易传播”的归纳。据其上下文,IDE自动导入让此类问题容易悄然积累。
- 原始内容:Architects consider the cyclic dependency shown in Figure 2-2 an antipattern because it presents difficulties when a developer tries to reuse one of the components—each of the entangled components must also come along. Thus, in general, architects want to keep the number of cycles low. However, the universe is actively fighting the architect’s desire to prevent this problem via convenience tools. What happens when a