GraphQLConf 2024

Building a GraphQL API as a solo developer handling both the front end and back end in a single Git repository can be straightforward. However, in a real-world scenario, you will need to collaborate with other developers, both within your team and externally. There will be API consumers under your control, as well as those you might not even be aware of. If you use composite schemas (such as Federation), many teams will create their subgraphs to compose a supergraph. How can you safely evolve your schema without breaking clients? How do you prevent attackers from sending vulnerable GraphQL operations to your server? A schema registry can assist you and your team in successfully adopting GraphQL at scale. Discover how to gain analytics on your GraphQL API usage, avoid shipping breaking changes through CI/CD integrations, and prevent unwanted GraphQL operations by leveraging Persisted Documents using the open-source MIT-licensed Hive API platform specially designed for GraphQL.