The Secrets to Wayfair’s Graph Success from Inception to General Availability
summary
Wayfair builds a Federated GraphQL platform with an opinionated Gateway, pilot programs and governance bodies, taking two years to GA after iterating through four governance proposals and three architecture options. The platform runs 220 million requests a day across 80 subgraphs, grows its community of 500 users about 5% month over month, uses hands‑on pilots, office hours and slack for feedback, and balances empowerment with guardrails to scale successfully.
AI-written summary · about
chapters (16)
- 0:00Introduction and mission
- 0:45Monolith challenges and need for change
- 1:48GraphQL Federation adoption and early struggles
- 2:32Key secrets to Wayfair’s graph success
- 3:14Engaging senior leaders for buy-in
- 3:56Patience and iterative progress
- 4:59Team culture and celebrating wins
- 5:42Stakeholder engagement framework
- 7:06Design phase and architecture alignment
- 8:31Cultural changes and education investment
- 9:14Rollout phase and pilot programs
- 10:36Pilot expectations and advocacy
- 11:21General availability and user feedback
- 11:41Leading senior leaders and expectations
- 12:24Balancing empowerment and governance
- 12:44Four principles for your journey
related talks
35mA Wild GraphQL Rollercoaster Ride a Federated GraphQL Adoption Story
45mFast, Flexible, and Federated: How Wayfair’s Schema-Driven UI Supercharges Experimentation
26mKeynote: Apollo's Journey with GraphQL: Transforming Enterprise APIs for the Future
23mBuilding the Graph at Booking.com
23mBuilding the Graph at Booking.com
30mDeep Learnings Migrating legacy services to Federated GraphQL
38mGraphQL Federation in the Wild
37mThe Future of GraphQL in the Enterprise Panel Discussion by GraphCMS