Problem
Paradox Shop's checkout service carries ~400 RPS of production load and needs a major runtime upgrade; a change big enough that it can't be rolled out gradually behind a small traffic percentage, and risky enough that the team wants an instant way back if anything's wrong. Design a release path from scratch where the old and new environments are EACH fully provisioned for the full ~400 RPS at once, traffic cuts over atomically from one to the other, and rollback means simply cutting back, with nothing to redeploy.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.