Everyone who has worked with GraphQL knows just how powerful and flexible this API query language is.

The first principle of Principled GraphQL is One Graph – the rule which encourages the implementation of a single graph to maximize the value of GraphQL. We want this ubiquitous API that exposes our business model in a much richer way.

But as our graph grows over time and multiple teams start working on it, we often hit a wall where they need to federate their graph to align its development with their organizational structure. We want to make sure that teams are not blocked in their flows to deliver new features to the customer.

In this talk, we will look at how we can distribute our GraphQL API into sub-graphs and the challenges and advantages that come along with distributed graphs.