GraphQL invalidates existing assumptions about how to best design client–server APIs, because it requires that we shift our mindset from server-driven API design to client-driven design. The result is more powerful and flexible, but introduces new challenges of its own. This talk highlights a few of those challenges, and proposes some best practices to manage them.
Slide text and presenter notes licensed under CC BY 4.0. Presentation rendered using Deckset.