Problem
Paradox Shop's next release renames a column the checkout service reads on every request. The rollout is a rolling deploy; for several minutes, both the old and new application versions run side by side, and both need to hit the same production database. The new version below has already been deployed, but it was never actually connected to the database, and the migration phase is still Complete (no schema change in progress). Fix the design so both versions work against the same database throughout the overlap window.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.