知识卡片
接口独立演进须保护消费方
团队能独立发布的前提是兼容策略与消费方约定清楚,不能把可自行推接口变更等同松耦合。错误处理也需清楚语义和可接受降级,使未预期输入不会被包装成假成功。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 重构与技术债
原书出处 · 1 处
- · 查看原书依据
Loosely coupled architecture No clear view on a system’s architecture and responsibilities, and how it interacts with upstream and downstream dependencies. Too many dependencies on other systems; unnecessary runtime coupling. Cannot release a change to production without depending on or being blocked by one or more teams. Components are loosely coupled. A team owning a system can release an interface change without depending on other
参考来源
- 位置:《Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)》第08章《重构与技术债》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Effective Machine Learning Teams (David Tan, Ada Leung, David Colls)/_epub-src/OEBPS/ch08.html)
- 结论依据:摘录中关于接口独立演进须保护消费方的定义、比较或条件支撑卡片;原书表述不严谨的范围已在覆盖记录逐项限定,不把案例结果外推为普遍结论。
- 原始内容:Loosely coupled architecture No clear view on a system’s architecture and responsibilities, and how it interacts with upstream and downstream dependencies. Too many dependencies on other systems; unnecessary runtime coupling. Cannot release a change to production without depending on or being blocked by one or more teams. Components are loosely coupled. A team owning a system can release an interface change without depending on other