@krishnachaytanya: Zero-downtime database migration: how you change a live table while users are still hitting it. Run ALTER TABLE to change a column type and Postgres locks the whole table. Every query waits. That is your downtime. So instead of editing the track under a moving train, you build a new one beside it: EXPAND: add the new column BACKFILL: copy old rows over in batches SWITCH: flip reads to the new column mid-flight (writes go to both during the overlap) CONTRACT: drop the old column The train never stops. 0 queries dropped. Postgres, plus GitHub's gh-ost and Stripe, migrate exactly this way. Save this for your next schema change. Which step trips people up most: the backfill or the switch? #systemdesign #database #postgres #backend #softwareengineering
Is this a hot spare environment or is it upon open failure swap? Since you said migration you have to take moving active traffic tables and sessions or have them on an another device
2026-09-04 15:53:25
3
alt+control+start :
interesting demo
yeah db migrations are tough
usually a stop for writes is how we do it and then perform the upgrade
2026-09-06 06:44:27
0
To see more videos from user @krishnachaytanya, please go to the Tikwm
homepage.