Panel - Championing Your Supergraph After Launch, Now What?
summary
After launch the focus shifts to measurable operations: set up metrics, tracing and dashboards, track latency, cache hit rates and error rates over time, and tie cache savings to dollars. Expect to find surprises — Expedia measured a 36% reduction in client code after GraphQL adoption — and use correlation IDs to trace slow resolvers back to specific services. Establish onboarding templates, a Champions guild for schema proposals, and a governance ladder (four stewardship levels) so ownership, resolution time, adoption rate, and cost attribution are all observable and accountable.
AI-written summary · about
chapters (5)
- 0:00Introduction and context
- 5:03Observability in production
- 11:30Demonstrating supergraph value
- 20:23Governance and stewardship
- 25:17Final thoughts and Q&A
related talks
42m4 Steps to a Successful GraphQL API Program
26mKeynote: Apollo's Journey with GraphQL: Transforming Enterprise APIs for the Future
10mKeynote: Creating a Golden Path for GraphQL
35mA Wild GraphQL Rollercoaster Ride a Federated GraphQL Adoption Story
26mIncrementally Adopting GraphQL. The Holy Grail?
32mSponsored Session: Championing GraphQL Client in a Modern Platform
28mPanel Discussion: The GraphQL Production Roundtable
23mHow (not) to run a Graphql Stewardship Group