知识卡片
权衡先找缠结维度
权衡分析先发现哪些部分互相牵动,再分析如何耦合,最后评估改变某维度对其他部分的影响。静态图包含启动和运行必需的操作系统、库、存储、代理与集成,不把仅在一次业务流程中协作的服务误算为静态依赖。可利用部署自动化生成依赖文档;运行流程另建动态模型。维度由当前生态和约束发现,书里的通信、一致性与协调只是起点。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 构建自己的权衡分析 · 查看原书依据
The static coupling diagram does not consider other quanta whose only coupling point is workflow communication with this quantum. For example, if an AssignTicket Service cooperates with the ManageTicket within a workflow but has no other coupling points, they are statically independent (but dynamically coupled during the actual workflow).
参考来源
- 位置:《Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)》第15章《Chapter 15. Build Your Own Trade-Off Analysis》(来源项目: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/ch15.xhtml)
- 结论依据:原文的定义、示例或失败路径支持以下归纳:权衡分析先发现哪些部分互相牵动,再分析如何耦合,最后评估改变某维度对其他部分的影响。 其他条件结合本章同小节说明;不将模式目标当成已有运行保证。
- 原始内容:The static coupling diagram does not consider other quanta whose only coupling point is workflow communication with this quantum. For example, if an AssignTicket Service cooperates with the ManageTicket within a workflow but has no other coupling points, they are statically independent (but dynamically coupled during the actual workflow).