How are you doing your tests? Are you effectively covering all use cases and their unique nuances? How many times have you broken everything? 

Let's delve into the complexities of testing a federated supergraph at scale, discuss on what are the issues and limits of testing GraphQL today and options for improving testing and increase confidence.

Turning a private GraphQL API into a public one comes with unexpected challenges. We’ll share how we approached this transition—starting from an existing internal schema that wasn’t shaped for external consumers—and the steps we took to expose only what was ready. Using Apollo Federation Contracts, we filtered out unstable or sensitive parts of the graph. Along the way, we defined best practices for the public schema, like cursor-based pagination, using oneOf for inputs and results. We’ll also touch on how we serve the schema through Hive Gateway with a supergraph setup, and the security measures we added, like depth limiting and complexity analysis. To keep things evolving safely, we rely on GraphQL Hive to track usage and guide deprecations.

If you’re thinking about exposing a GraphQL API—or just want ideas for keeping one clean and manageable—this talk will share what worked for us, what didn’t, and what we learned.

An open discussion with GraphQL experts and the audience live in New York City to chat about what they're seeing in the GraphQL space 🙌🗽

From the initial consideration to implementing a federated model. Learn how domain-driven design has influenced American Express practical approach and helped us in developing a big GraphQL Federated API also revamping the quality of our APIs.