知识卡片
接口生命周期约束消费者预期
API 从计划、试用、正式运行、弃用到退役,各阶段对消费者的稳定性承诺不同。试用阶段可收集反馈并调整契约;正式版本变更要管理兼容;弃用阶段继续可用但应通知迁移,最后才移除。状态公告和使用量指标应与路由策略配合。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- · 查看原书依据
The planning stage is about advertising that you are building an API and gathering initial feedback on the design and shape of the API from consumers. This allows a discussion about the API and the scope, allowing any early design decisions to be included. Beta Involves releasing a version of our API for users to start to integrate with; however, this is generally for the purpose of feedback and improving the API.
参考来源
- 位置:《Mastering API Architecture》第5章《Deploying and Releasing APIs》之《API Lifecycle》(源文件:_epub-src/OEBPS/ch05.xhtml)
- 结论依据:原文按 Planned、Beta、Live、Deprecated、Retired 描述不同阶段的消费者预期和兼容要求。
- 原始内容:The planning stage is about advertising that you are building an API and gathering initial feedback on the design and shape of the API from consumers. This allows a discussion about the API and the scope, allowing any early design decisions to be included. Beta Involves releasing a version of our API for users to start to integrate with; however, this is generally for the purpose of feedback and improving the API.