知识卡片
先稳契约再分散实现
把跨团队API契约与各队内部实现分开决定,可以先明确共同预期,再并行开发。契约须足够容纳所有消费者的必要需求,消费者驱动契约及持续验证可提供破坏变化预警。共享部分因承载后续选择可能值得花更多时间,不能以小决定为由匆忙定错。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Tackling Architectural Variability · 查看原书依据
You can also split large decisions by seeking out the smallest decision (or decisions) that are needed for delivery work to start. This means splitting decisions into those that are shared among teams first and proceeding to the single-team-focused decisions afterward. For example, split out the decisions about an API between two teams from decisions
参考来源
- 位置:《Facilitating Software Architecture》第13章《Tackling Architectural Variability》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch13.html)
- 结论依据:原文unblocking flow段讨论API、contract tests、Pact及承载后续决定的共享契约。
- 原始内容:You can also split large decisions by seeking out the smallest decision (or decisions) that are needed for delivery work to start. This means splitting decisions into those that are shared among teams first and proceeding to the single-team-focused decisions afterward. For example, split out the decisions about an API between two teams from decisions