How GraphQL Servers Break and How to Harden Your Resolvers
summary
Claims that Solo.io’s GraphQL Envoy filter lets teams harden resolvers with no code by using declarative resolvers and JQ transformations, running in Kubernetes + Istio/Envoy. Demo shows a failing productpage v2 returning 503s, an outlier detection policy ejects an endpoint after one consecutive error and re-adds it after a 60s base ejection time, after which requests resume healthy responses. Config-managed retries, failover and circuit breaking live in the proxy not in resolver code.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:15Who we are
- 1:33Goals
- 2:35Resolvers
- 4:24Kubernetes
- 5:46Passive Health Checking
- 8:57Another Proxy
- 9:35Other Proxy Types
- 11:12Declarative Resolvers
- 15:29Demo
related talks
15mHarnessing GraphQL for Efficient API Queries: Learn How
24mSupercharging GraphQL with Envoy: Unveiling the Efficiency of Declarative GraphQL
55mMastering GraphQL: Strategies from the Experts
24mA GraphQL Survival Kit
01h 27mMr. Toad’s Wild Ride: A Rollicking, Declarative GraphQL Workshop
08mLightning Talk: Resolvers Everywhere: Rethinking Client and Server Boundaries in GraphQL
32mHow to Not Break Your GraphQL Clients
35mGraphQL in the Enterprise