How to Choose a GraphQL Gateway
summary
Benchmarks compare real-world Gateway setups using Apollo Federation v1 with multiple subgraphs implemented in Rust so upstreams never bottleneck tests run on GitHub Actions across 1–4 CPUs and show Wondergraph and Apollo Router near the top while a tuned Node.js GraphQL Mesh rivals them; plans include bare metal runs with Chillicream for stabler numbers. A new open source Gateway called Conductor in Rust targets federation v1/v2, Fusion and persisted operations and aims for low CPU/memory and extensible caching, rate limiting and tracing.
AI-written summary · about
chapters (6)
- 0:00Introduction to The Guild
- 1:08The role of GraphQL gateways
- 3:59Core functionality of gateways
- 11:25Benchmarking gateway performance
- 18:07How to choose a gateway
- 25:01Introducing Conductor
related talks
07mThe future of GraphQL routing
23mWas It Worth It? Lessons from Implementing Two GraphQL Routers. In JavaScript & Rust
01h 05mBuilding Distributed GraphQL APIs
38mInside Booking.com’s Router Rollout: Powering Product and Platform at Massive Scale
38mGraphQL Federation in the Wild
31mLessons from Scaling GraphQL to Half a Billion Requests per Minute
20mThe State of GraphQL Federation
36mGraphQL Federation - The @key to Your Platform API Strategy