API / Apollo Gateway Interview questions
Why doesn't Apollo Gateway support GraphQL subscriptions as robustly as Apollo Router does?
Apollo Gateway's Node.js implementation was designed around federated execution of queries and mutations; federated subscriptions — where a long-lived connection needs to be composed and kept open across multiple subgraphs — were never a first-class design goal for it, so support is limited at best.
Apollo Router, by contrast, was built with subscriptions in mind from early on. It supports both HTTP callback-based subscriptions and WebSocket-based subgraph subscriptions, and can compose subscription fields across subgraphs the same way it composes queries.
This is one of the concrete, technical reasons teams cite when migrating off Gateway — if a graph needs real-time federated subscriptions, Router isn't just faster, it's the option that actually supports the feature end-to-end.
More Related questions...