知识卡片

普通读书笔记卡 · 3328.f

共享库放大二进制耦合

理解等级:高级

面向全公司的内部共享库会把各产品的依赖版本绑在一起:库升级可能迫使多团队同步迁移,也可能让团队规避库而重复造轮子。共享应围绕稳定契约与真实复用评估,不能仅因平台团队能发布就统一下发。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    原书出处

    参考来源

    - 位置:《Principles of Software Architecture Modernization》第2章《Anti-Patterns: Lack of Isolation》(源文件:`_epub-src/OPS/ch02.xhtml`,归一化正文 [29502:33636)) - 结论依据:原文说明全公司共享库会造成二进制耦合、强制迁移和重复实现,强调这种代码共享也是隔离缺口。 - 原始内容:But when you deliver global libraries to the whole company, you have different concerns but with equal impact: bloated solutions that lead to binary coupling, forced waterfall migrations by product teams, people avoiding the library and thus duplicating code, duplications, and an array of other problems. Bad libraries by definition are not isolated: a platform team shipping bad, unnecessary shared libraries to the entire company couples them all together.