知识卡片
场景收窄真正的取舍
通用优缺点很多,只有业务相关场景能指出关键取舍。支付按类型拆服务,更新信用卡实现和新增积分支付会更灵活;多种方式混合支付却需要跨服务协调,损害性能与一致性。于是决策转成当前业务更需要性能一致性,还是扩展与交付敏捷。先建两种拓扑再演练实际变更及异常,能删掉无关指标,避免以“优点更多”机械投票。
此例具体应用了[[独立评分后合并矩阵]]的方法。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 构建自己的权衡分析 · 查看原书依据
Having modeled these three scenarios, the architect realizes that the real trade-off analysis comes down to which is more important: performance and data consistency (a single payment service) or extensibility and agility (separate services).
参考来源
- 位置:《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)
- 结论依据:原文的定义、示例或失败路径支持以下归纳:通用优缺点很多,只有业务相关场景能指出关键取舍。 其他条件结合本章同小节说明;不将模式目标当成已有运行保证。
- 原始内容:Having modeled these three scenarios, the architect realizes that the real trade-off analysis comes down to which is more important: performance and data consistency (a single payment service) or extensibility and agility (separate services).