知识卡片
框架升级更应及时
框架调用业务代码并构成应用骨架,通常比按需调用的库形成更广依赖。跨越多个大版本再升级往往更痛苦,因此应尽早评估稳定更新。原书“库被动升级”属于结构耦合视角,不能扩展为忽略库的安全漏洞或兼容风险。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 框架升级更应及时
原书出处 · 1 处
- Building Evolvable Architectures · 查看原书依据
Because frameworks are a fundamental part of applications, teams must be aggressive about pursuing updates. Libraries generally form less brittle coupling points than frameworks do, allowing teams to be more casual about upgrades. One informal governance model treats framework updates as push updates and library updates as pull updates. When a fundamental framework (one whose afferent/efferent coupling numbers are above a certain threshold) updates, teams
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第07章《Building Evolvable Architectures》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch07.html;段落定位:Because frameworks are a fundamental part)
- 结论依据:原文对“框架升级更应及时”的定义或案例,支撑“框架调用业务代码并构成应用骨架,通常比按需调用的库形成更广依赖”的归纳。据其上下文,跨越多个大版本再升级往往更痛苦,因此应尽早评估稳定更新。
- 原始内容:Because frameworks are a fundamental part of applications, teams must be aggressive about pursuing updates. Libraries generally form less brittle coupling points than frameworks do, allowing teams to be more casual about upgrades. One informal governance model treats framework updates as push updates and library updates as pull updates. When a fundamental framework (one whose afferent/efferent coupling numbers are above a certain threshold) updates, teams