← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1458.f.5.b.1.a

API版本从首版规划

理解等级:高级

公共API更新不能指望所有用户同步修改客户端,需从第一次设计就安排版本,并让负载均衡可按标准字段路由到正确版本。客户端库可封装变化、改善体验,但多种语言环境会增加维护负担。优先采用已普及标准,可减少用户学习;这些便利仍须与兼容和维护成本一起评价。

相关:[[接口早设计晚公开]]。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 理解用户体验 · 查看原书依据

      Finally, we must version our APIs from the first design. Once the design is adopted, it is tough to ask customers to change their code, and the only way to update an API is to release new versions. While designing, we should communicate versioning in a manner that enables the standard load balancer to reroute requests to correct versions (e.g., via HTTP headers).

    参考来源

    - 位置:《Software Architecture and Decision-Making》第4章《理解用户体验》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch04.xhtml) - 结论依据:原文的定义、比较或例子支持“公共API更新不能指望所有用户同步修改客户端,需从第一次设计就安排版本,并让负载均衡可按标准字段路由到正确版本”;正文据此说明用途和边界。 - 原始内容:Finally, we must version our APIs from the first design. Once the design is adopted, it is tough to ask customers to change their code, and the only way to update an API is to release new versions. While designing, we should communicate versioning in a manner that enables the standard load balancer to reroute requests to correct versions (e.g., via HTTP headers).