Flip the Switch Slowly
summary
A legacy exam system with millions of rows and millions of hits per month gets migrated without downtime by recording every action into an events table, projecting those events into both the old and new schemas, and slowly backfilling historical events while verifying mirrors match. Uses Laravel, Nginx traffic splits (5%→95%), and the verbs package to event‑source models; migration runs in production for months, sees no rollback, and ships into multiple apps.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:51The legacy code challenge
- 5:39The problem with legacy data
- 10:01A case study in migration
- 16:28Introduction to event sourcing
- 20:51Implementing the migration
- 25:07Deployment and benefits
- 28:31Verbs package and updates
- 33:11Q&A and closing
related talks
01h 06mRewriting Legacy Code
01h 02mRewriting 12-Year-Old Code
24mArchitecting a Seamless E-commerce Platform Transition
43mLegacy Architecture Migration Patterns with DDD
19mMigrating from legacy platforms to node
38mA How-to guide for migrating legacy data applications
24mDatabases beyond the tutorials
31mTricks and treats for new developers