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.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Apollo persisted queries send an operation ID instead of the full GraphQL document, shrinking request payloads and enabling server-side plan reuse.
Use a cache update function with Apollo Client InMemoryCache to merge mutation results locally and avoid unnecessary refetches. Includes verification steps and limits.
Learn how to set Apollo Client InMemoryCache field policies for offset/limit and cursor-based pagination so fetchMore merges pages correctly without duplicates.
Learn how Apollo’s persisted‑queries feature shrinks request size, hardens security, and what you need to keep in sync. A step‑by‑step guide, example config, and trade‑offs are included.
Configure Apollo Client 3's InMemoryCache to merge paginated GraphQL pages instead of replacing them, with fetch-policy trade-offs and verification steps.
The Apollo Router uses @requires and @provides directives to compose cross-subgraph query plans, fetching providing fields before requiring resolvers.
Apollo Client's InMemoryCache normalizes entities by ID, which breaks offset-based pagination when limit/offset aren't part of the cache key. Learn two fixes—fetchPolicy 'network-only' or custom typePolicies with keyArgs—and when each applies.
When Apollo Client returns PersistedQueryNotFound or PersistedQueryNotSupported, the server can’t process the query ID. This guide walks through the common causes, diagnostic steps, and fixes to get your persisted queries working again.
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.