知识卡片
复用前计算跨团队代价
共享库的复用收益不能只按少写代码计算。还要估计版本迁移、库所有者排期、故障调查和跨团队协调;当一段简单逻辑引入沉重依赖时,局部实现可能更便宜。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第3章《Anti-Patterns: Distributed Monoliths》(源文件:`_epub-src/OPS/ch03.xhtml`,归一化正文 [42008:46189))
- 结论依据:原文追问共享库的灵活性与协调代价,并指出团队常把复用视为当然,却未审视其负面影响。
- 原始内容:What’s the benefit? Is it worth it? Teams have good intentions, but distributed monoliths eat good intentions and create coupling and negative effects. Putting hundreds of services and libraries in this picture becomes chaos. The scenarios we’ve illustrated here are common, and happen every day in our industry; they happen because people take reuse for granted and don’t examine the potential drawbacks.