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 hit the same production database. Design a schema-change strategy from scratch where both versions keep working against the same database throughout the overlap window, instead of the old version's queries breaking the moment the migration runs.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.