Building the Graph at Booking.com
summary
Booking.com breaks a 25+ year monolith into a federated Graph, first migrating search results and property pages and then iOS/Android via a GraphQL wrapper over existing BFFs. Traffic grows from 50 billion operations to 100 billion operations in 90 days with peaks ~1.6 billion daily. Front-end teams report up to 40% faster time‑to‑market. The team centralizes translations on the Graph, discovers a client-side data leak (paused rollout), and mitigates extra backend pressure by asking larger composed queries.
AI-written summary · about
chapters (13)
- 0:00Graph at Booking.com
- 1:29Modernizing the monolith
- 2:52Selling the graph internally
- 6:46Planning distributed migration
- 8:11Modernizing search and pages
- 9:16Migrating mobile clients
- 11:03Lessons learned
- 13:53Schema-first with GraphQL
- 15:19Faster development cycles
- 16:42Centralizing business logic
- 18:29Usage growth and scaling
- 19:31Expanding interoperability
- 20:33Q&A
related talks
40mAgent-Ready Graphs: Engineering the Foundations for Discoverability, Safety, and QoS
38mInside Booking.com’s Router Rollout: Powering Product and Platform at Massive Scale
30mDeep Learnings Migrating legacy services to Federated GraphQL
33mBooking.com tech modernisation
29mScaling the Data Access by Leveraging GraphQL Federation for Service to Service Communication
34mRealtor.com's Technological & Cultural Transformation with GraphQL
46mMoving to GraphQL
42mPanel - Fortune 100 Graphs - Powering Today's Need and Tomorrow's Trends