返回主题:构件化设计与组装

知识卡片

普通读书笔记卡 · 2304.g

组件依赖图估计拆分难度

理解等级:高级

组件依赖只统计跨命名空间引用,不把组件内部类关系混在同一张图。依赖稀少常可通过移动与重构分离;依赖密集时可能必须混合重写,极端缠绕可能根本不宜拆。图帮助估计可行性、工作量和改造路线,不能把本书高尔夫球、篮球、飞机的类比当精确工期。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 基于组件的分解模式 · 查看原书依据

      The purpose of the Determine Component Dependencies pattern is to analyze the incoming and outgoing dependencies (coupling) between components to determine what the resulting service dependency graph might look like after breaking up the monolithic application.

    参考来源

    - 位置:《Software Architecture: The Hard Parts》第5章《基于组件的分解模式》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch05.xhtml) - 结论依据:原文的定义、比较或案例支持“组件依赖只统计跨命名空间引用,不把组件内部类关系混在同一张图”;正文据此解释其用途与适用边界。 - 原始内容:The purpose of the Determine Component Dependencies pattern is to analyze the incoming and outgoing dependencies (coupling) between components to determine what the resulting service dependency graph might look like after breaking up the monolithic application.