Make database changes deployable
Sequence a schema change so old and new application versions remain compatible during deployment.
Schema risk The team wants a field rename. Old app versions read full_name; new app versions read display_name. The danger is not the SQL itself. The danger is old and new code meeting a schema that only one of them understands. Expand-contract Compatibility first, cleanup later Make the database support both old and new application behavior during the deployment transition. Rename in place Fast on paper, brittle during rollback. Deployments and rollbacks remain boring because both versions can run. When deployment is a sequence, compatibility is the safety rail. 01 Expand 02 Write 03 Read 04 Contract
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in