Workshop: Scaling and Securing API Development with a GraphQL Platform
summary
Hands-on demo builds a composed supergraph from four subgraphs using the Hive schema registry, spins a Gateway that pulls the supergraph (no introspection) and routes queries to services, and records analytics from about 20 test requests so field usage appears in the dashboard. CI runs schema checks before publish and an automated rule marks breaking changes safe if they affect 0% of traffic over seven days so a removal is accepted after 35 reported requests. App version 1.0.0 publishes two persisted documents and the Gateway enforces them, replacing raw queries with hashes and preventing arbitrary operations with conditional breaking changes.
AI-written summary · about
chapters (7)
- 0:00Introduction to workshop
- 2:06Why schema registry matters
- 7:49Setting up GraphQL Hive
- 18:15Configuring GraphQL Gateway
- 33:19Safely evolving GraphQL schema
- 47:41Securing Gateway with persisted docs
- 1:05:07Q&A and closing
related talks
27mHow The Guild is using GraphQL at scale
50mDistributed GraphQL APIs: Breaking Down Monoliths & Unlocking Agility for Dev Teams
56mDistributed GraphQL APIs
59mBuilding Distributed GraphQL APIs
01h 05mBuilding Distributed GraphQL APIs
28mBuilding a distributed graph w/ Apollo Federation
42m4 Steps to a Successful GraphQL API Program
32mHow to get started and build something with GraphQL