Reduce GraphQL Request Size with Apollo Persisted Queries
Apollo persisted queries send an operation ID instead of the full GraphQL document, shrinking request payloads and enabling server-side plan reuse.
Loading…
ReadMeFeed / Community knowledge
#apollo-graphql
Real questions. Useful conversations. Find the people who know your stack.
Diagnosing and Fixing ‘Missing Field’ Errors in Apollo GraphQL
Apollo GraphQL missing field errors usually stem from schema mismatches or stale client caches. This diagnostic guide shows how to check the server schema, inspect the cache, regenerate types, and escalate when needed.
Reducing Perceived Latency with the @defer Directive in Apollo GraphQL
Stop letting slow resolvers block your entire UI. Learn how to use the @defer directive in Apollo GraphQL to stream partial results and improve perceived performance.
Apollo Federation: Stitch Two Subgraphs into a Single Gateway
Learn how Apollo Federation stitches independent GraphQL services into a single schema, with a step‑by‑step example, common pitfalls, and verification tips.
apollographql
graphqlSplitting One Graph Across Teams: Apollo Federation v2 with @key, @requires, and @provides
Apollo Federation v2 lets each team own a subgraph while clients query one graph. Here's how @key, @requires, and @provides coordinate it, with a verifiable example.
Resolving Entities Across Apollo Federation Subgraphs with @key and resolveReference
Split a GraphQL API into Apollo Federation subgraphs and resolve a shared entity across them using the @key directive and __resolveReference resolvers, with verification steps and pitfalls.
nodejsManaging Apollo Client Cache Normalization and Local State
Learn how to implement Apollo Client cache normalization and local state management to ensure UI consistency and reduce redundant network requests.
Apollo Client cache persistence: schema version mismatch during hydration
Apollo Client utilizes apollo3-cache-persist to mirror the in-memory cache to local storage, enabling state recovery across browser sessions. During the hydration phase, the client restores the persisted state to the InMemoryCache before the application becomes interactive. A challenge arises when the application schema is updated between sessions. If the pe
Automatic Persisted Queries (APQ) hash-cache consistency in distributed clusters
Apollo Server Persisted Queries Automatic Persisted Queries (APQ) optimize network latency by replacing full query strings with SHA-256 hashes. In a standard Apollo Server configuration, the server maps these hashes to the original query strings in a local cache to avoid the overhead of transmitting large payloads on every request. When deploying Apollo Serv