Panel Discussion: The GraphQL Production Roundtable
summary
Large orgs describe concrete defenses: an operation registry with trusted documents, adaptive concurrency using a Netflix library, and traffic sharding after a “query of death” incident that infinite‑loops and forces two production shards to contain the blast radius. CI bots run schema linting and an AI review bot plus a graph doctor that flags breaking changes, with an experimental directive to opt into unstable fields and weekly automated PRs that delete unused fields driven by production metrics from a platform that hosts 600 tenant modules.
AI-written summary · about
chapters (7)
- 0:00Welcome and panel intro
- 1:44Flexibility and its costs
- 7:06Schema governance at scale
- 13:51Onboarding and training engineers
- 18:29Federation challenges
- 24:08Starting from scratch today
- 28:01Closing remarks
related talks
44mPanel - Graph Leadership - Scaling the Graph Across Your Org and Platform
42mPanel - Fortune 100 Graphs - Powering Today's Need and Tomorrow's Trends
48mAPI Optimization Tale: Monitor, Fix and Deploy (on Friday)
47mPanel - Modernization Stories - Monoliths, Migrations and Mergers
23mBlueprints of Successful GraphQL Architectures
37mThe Future of GraphQL in the Enterprise Panel Discussion by GraphCMS
42m4 Steps to a Successful GraphQL API Program
27mPanel - Championing Your Supergraph After Launch, Now What?
