問題文
A team wants to shorten the window in which a bad release affects users, and their service has no compatibility constraint between versions. Which pattern gives them that directly?
選択肢
- Publishing the artifact with an identifier that resolves by content, because a release that can be identified exactly can also be withdrawn exactly, which removes the ambiguity that makes a rollback slow.
- A canary release, because only a small share of traffic reaches the new version while it is being observed.
- Shortening the reconciliation interval, because a shorter interval means the corrected declarations reach the runtime sooner once the problem has been noticed and a fix has been recorded.
- A blue-green switch, because the switch itself is a single step.