知识卡片

普通读书笔记卡 · 1466.k

小步改造先验证收益

理解等级:高级

改造既有服务应先选一个明确问题,用可独立发布的小改动观察可衡量收益,再决定后续投入。把很多关键修改合进一次发布,既增加故障范围,也使效果难以归因。性能、稳定性或更新成本的改善需要实际观察,不能仅因接口更像某种风格就认定改造成功。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 结语:按收益渐进采用配方 · 查看原书依据

      Like any transformation work, it only pays off if there are clear advantages to changing an already existing system. The best strategy is to make a number of independent, small changes over time instead of trying to package up a lot of important modifications in a single production release. You can use the recipes in this book to identify a single problem (e.g., “How can we improve the performance of our data queries?”), and then work through one or more changes to your services and/or interface APIs that will result in measurable improvements. Focusing on making changes that result in measurable improvements has a kind of “flywheel” effect in the company. As each change brings better performance, a more stable runtime experience, and less resource-intensive updates, this adds momentum to your work and makes it easier to get support throughout the organization for other improvement initiatives in the future.

    参考来源

    - 位置:《RESTful Web API Patterns and Practices Cookbook》Chapter 8. Closing Remarks(来源项目book-sources,源文件:extracted/RESTful Web API Patterns and Practices Cookbook Connecting and Orchestrating Microservices and Distributed Data (Mike Amundsen)/_epub-src/OEBPS/ch08.xhtml) - 结论依据:原文直接给出相应职责、操作或比较;本卡保留其用途与适用边界,不将历史接口表述当作当前工具验证。 - 原始内容:Like any transformation work, it only pays off if there are clear advantages to changing an already existing system. The best strategy is to make a number of independent, small changes over time instead of trying to package up a lot of important modifications in a single production release. You can use the recipes in this book to identify a single problem (e.g., “How can we improve the performance of our data queries?”), and then work through one or more changes to your services and/or interface APIs that will result in measurable improvements. Focusing on making changes that result in measurable improvements has a kind of “flywheel” effect in the company. As each change brings better performance, a more stable runtime experience, and less resource-intensive updates, this adds momentum to your work and makes it easier to get support throughout the organization for other improvement initiatives in the future.