How to ship a breaking schema change with zero downtime using expand and contract
Making a backward-incompatible column, table, or store change safe to ship while old and new application code run at once, by staging it across several releases that each stay compatible with the one before.
Subscriber section
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.