返回主题:软件质量属性的取舍

知识卡片

普通读书笔记卡 · 3352.c.5

正确情境改写优劣排序

理解等级:高级

共享库的性能、容错与扩展性在通用表中可能胜出,但若当前系统用四种语言、共享代码频繁变化,真正驱动决策的是异构复用、变更和依赖管理,共享服务反而更合适。评估应先筛出本场景有价值的指标,再比较相关代价。图15-3与15-4使用同一张表,仅因业务情境明确而改变选择,说明累计优点数量不是可靠决策法。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 构建自己的权衡分析 · 查看原书依据

      This process emphasizes two important observations. First, finding the best context for a decision allows the architect to consider fewer options, greatly simplifying the decision process. One common piece of advice from software sages is “embrace simple designs,” without ever explaining how to achieve that goal. Finding the correct narrow context for decisions allows architects to think about less, in many cases simplifying design.

    参考来源

    - 位置:《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) - 结论依据:原文的定义、示例或失败路径支持以下归纳:共享库的性能、容错与扩展性在通用表中可能胜出,但若当前系统用四种语言、共享代码频繁变化,真正驱动决策的是异构复用、变更和依赖管理,共享服务反而更合适。 其他条件结合本章同小节说明;不将模式目标当成已有运行保证。 - 原始内容:This process emphasizes two important observations. First, finding the best context for a decision allows the architect to consider fewer options, greatly simplifying the decision process. One common piece of advice from software sages is “embrace simple designs,” without ever explaining how to achieve that goal. Finding the correct narrow context for decisions allows architects to think about less, in many cases simplifying design.