← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1841.h.1.a.11

适应度驱动架构设计

理解等级:高级

当成功依赖严格的架构能力时,先定义并实现该能力的评价,再以反馈筛选设计。LMAX案例用吞吐与底层测量发现上下文切换成本,改用更适合的执行结构。案例性能数值不是所有Java系统的承诺,重要的是以测量驱动选择并保留回归保护。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Building Evolvable Architectures · 查看原书依据

      A common practice in agile software development is test-driven development, where developers write unit tests before writing the corresponding functionality. A similar process can be used in architecture, particularly when the success of the application depends on meeting some stringent capabilities. Building a fitness function that governs that capability to help drive design ensures that it stays top of mind as the architect designs other

    参考来源

    - 位置:《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;段落定位:Building a fitness function that governs that capability) - 结论依据:原文对“适应度驱动架构设计”的定义或案例,支撑“当成功依赖严格的架构能力时,先定义并实现该能力的评价,再以反馈筛选设计”的归纳。据其上下文,LMAX案例用吞吐与底层测量发现上下文切换成本,改用更适合的执行结构。 - 原始内容:A common practice in agile software development is test-driven development, where developers write unit tests before writing the corresponding functionality. A similar process can be used in architecture, particularly when the success of the application depends on meeting some stringent capabilities. Building a fitness function that governs that capability to help drive design ensures that it stays top of mind as the architect designs other