知识卡片
暂留系统也要记录理由
暂留是基于收益与成本评估后先不迁移,并非遗漏。若改造 API 的回报不足,应明确告知相关方并用 ADR 留下决策依据、重新评估条件;这样后续团队能区分主动选择与拖延。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- · 查看原书依据
This is the do nothing (for now) strategy. Although it can be tempting to discount this approach, many architects (us included) will suggest you “pick your battles,” and sometimes the battle of migrating an API is not worth the return on your effort. This decision should, of course, be based on a sound business and technical evaluation, and you should communicate the decision to not
参考来源
- 位置:《Mastering API Architecture》第9章《Using API Infrastructure to Evolve Toward Cloud Platforms》之《Retain or Revisit》(源文件:_epub-src/OEBPS/ch09.xhtml)
- 结论依据:原文把 retain 定义为暂不行动,要求商业和技术评价、沟通及决策记录。
- 原始内容:This is the do nothing (for now) strategy. Although it can be tempting to discount this approach, many architects (us included) will suggest you “pick your battles,” and sometimes the battle of migrating an API is not worth the return on your effort. This decision should, of course, be based on a sound business and technical evaluation, and you should communicate the decision to not