Panel - Modernization Stories - Monoliths, Migrations and Mergers
summary
Panelists describe migrating by inserting an Apollo Router drop-in in front of a working monolith to get Federation in prod fast, then incrementally extracting subgraphs; teams build a Dev Portal, custom CLI, lints and CI checks, and use Apollo Studio for schema change previews and observability. Success signals are shorter CI/CD cycle times, faster PR-to-prod lifecycles, and measurable reuse that reduces services and costs. Governance runs as API stewards governance with review clinics and reference subgraphs to teach patterns.
AI-written summary · about
chapters (18)
- 0:00Introduction to modernization stories
- 1:04Monolith to supergraph at Liberty Mutual
- 2:07Monolith to GraphQL at Pointecast
- 4:40GraphQL at Intuit QuickBooks Commerce
- 7:10Federation at EV charging company
- 9:17Key themes in modernization journeys
- 11:04Proof of concept challenges
- 14:17Developer experience and tooling
- 18:11Learning while doing with monolith
- 21:21Adopting Federation from existing GraphQL
- 24:10Knowledge sharing and training
- 27:24Sharing learnings across Intuit
- 30:54Benefits for new teams adopting GraphQL
- 34:24Federating the monolith strategy
- 37:30Mindset, plan and tooling in GraphQL
- 38:10Measuring success in modernization
- 43:31Modernization for small organizations
- 47:06Closing remarks and Q&A
related talks
32mFrom Monolith to Micro Frontend
40mMigrating from a monolith to a new service
36mThe State Management Rollercoaster
57mModularizing the Monolith
57mMigrating from a monolith to a new service
28mPanel Discussion: The GraphQL Production Roundtable
31mMigrating from Monolith to Microfrontends
31mMonolith to Microservices: A Guide to Seamless Transitions