知识卡片
选库需评估生命周期负担
采用第三方或内部库时,除了即时功能,还要评估维护者是否稳定、响应速度、依赖图、漏洞和未来方向。一个当前省时的库,可能把升级与安全修补成本转嫁给所有消费者。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第4章《Anti-Patterns: Internal Shared Libraries》(源文件:`_epub-src/OPS/ch04.xhtml`,归一化正文 [8221:12466))
- 结论依据:原文列出缺所有者、维护方向变化、慢响应、错误、庞大依赖图与安全漏洞等选库风险。
- 原始内容:Lack of ownership: What if there are no more maintainers? We covered the consequences of lacking software ownership in Chapter 3 , Anti-Patterns: Distributed Monoliths . Change of direction: What if the owner takes a completely different path than the one you depend on right now? Slow responsiveness: The maintainers could be slow, won’t take many PRs, or simply ignore you. Then what? Do you fork the code forever?