API design is hard, and it's even harder when trying to design an API for a core service used by many other teams. Traditional REST API's quickly multiply in both query parameters and endpoints, trying to present the data in a way that each of the different teams require, potentially massively multiplying development work.
GraphQL can help unlock the value of your API by helping to uncouple the consumers and owners of data by giving each consumers the freedom to request exactly the data they need. We'll explore how Dylan is using GraphQL for its next generation of APIs and helping teams operate across service boundaries and the lessons learned from advocating for, and adopting GraphQL.