Deep Learnings Migrating legacy services to Federated GraphQL - Christian Ernst, Booking.com At Booking.com we made the decision to move to GraphQL in order to modernize our monolithic front-end data providing services. Our journey started with the monograph, a singular service to provide all GraphQL data as a bridge between legacy and new. This service, owned by a small team, exploded in use receiving countless contributions across the company. We soon realised as a team this would not scale for an entire company. This talk focuses on our experience and our journey from our first steps into the world of GraphQL and then our leap to move to a Federated GraphQL layer. We will share some of our most important learnings from the challenges we faced, including scaling and resiliency, bringing on legacy services, and multi cloud support and how we are handling these challenges via our ongoing initiatives and what we think the future of GraphQL at Booking.com looks like. GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools. Get Started Here: https://graphql.org/