A Wild GraphQL Rollercoaster Ride a Federated GraphQL Adoption Story
summary
bol overhauls its shopping stack starting 2020, builds a production product page on a federated GraphQL architecture using a Gateway, connectors (REST→GraphQL) to onboard legacy services, and a schema registry (Guild) plus stewardship and community processes. Time‑to‑market drops from 36h→<30m (~80x) for some flows. Adoption scales from one page to ~10 teams then a ~20‑engineer support group; native subgraph rollouts replace connectors, latency stays in single‑digit milliseconds and migration continues.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 6:26Assignment and research phase
- 10:00Building the first page
- 15:21Scaling to domain level
- 21:47Schema evolution and stewardship
- 24:57Full-scale migration
- 27:51Achievements and next steps
- 29:16Giving back to the community
related talks
30mDeep Learnings Migrating legacy services to Federated GraphQL
23mHow GraphQL Helped Create Scalability and Stability in the Retirement Space.
46mMoving to GraphQL
06mEscape the GraphQL Monolith
42mPanel - Fortune 100 Graphs - Powering Today's Need and Tomorrow's Trends
06mStreamlining how you shop: Walmart and GraphQL
42mFrom REST to distributed GQL
19mBringing GraphQL to the Enterprise: When IBM met Apollo
