Migrate the database without breaking deploys

Migration A column rename collides with rolling deploys. The database is shared state; old and new code must overlap safely. The migration path Expand -> migrate -> contract Make the schema accept both worlds before moving code to the new world. Direct rename Clean diff, unsafe overlap. Rolling deploys and rollback stay survivable. The database must support old and new application versions during transition. 01 Expand 02 Switch 03 Contract First release You need display_name but full_name is still read by existing pods and jobs.

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in