
You are preparing a production deployment for a critical backend service, and you want a clear plan in case the release causes errors, latency spikes, or downstream failures after traffic is shifted. The goal is not just to undo the change, but to restore service safely, minimize rider and driver impact, and avoid making the incident worse during a high-pressure rollout.
How would you design a rollback plan for a failed production deployment?