Changing Lanes with Lyft
summary
Lyft switches its web fleet to NextJS and builds a migration layer called Lyft Service that wraps core NextJS and adds a plugin system using webpack tappable plus jscodeshift codemods to automate upgrades. Teams run hands‑on migration sessions, preserve React Router during phased moves, and migrate services incrementally. Outcomes are concrete not vague: migrate over 100 micro-services, developer edit reloads fall from about 10–12 seconds to 350 milliseconds, example page bundle shrinks by 845 KB and 10,000 lines removed per service.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:16Changing Lanes with Lyft
- 2:21Identify Core Issues
- 4:25Look to Open Source
- 5:59Figuring out the rest
- 6:46Communicate early
- 7:02Building @lyft/service
- 8:24Test Environment
- 8:48Beta Tests
- 10:42Migration sessions
- 12:11Results
related talks
22mPlatform-powered: Building a Frontend Platform to Scale
13mSpeed at Scale: Optimizing The Largest CX Platform Out There
30mFrom Four Wheels to Two
32mHow Lyft Used Envoy to Rethink Microservice Development
17mSpeed at Scale: Optimizing The Largest CX Platform Out There
25mSpeed at Scale: Optimizing The Largest CX Platform Out There
21mMigrating critical apps to React
31mLessons learned migrating complex software