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.
Decide between persisted query hashing and dynamic queries in Apollo Server to optimize for latency, security, and developer velocity.
Persisted queries replace full GraphQL documents with operation hashes, but automatic registration still sends the full text on first use. Verify your server's behavior before relying on it as an allow-list.
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.
Persisted queries replace full GraphQL strings with short hashes, reducing bandwidth and enabling safe allow‑list enforcement in large‑scale APIs.
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.
Learn how GraphQL persisted queries replace large query bodies with short hashes, reducing bandwidth and boosting HTTP caching, with a concrete Apollo Server/Client setup and verification steps.
Persisted queries replace full GraphQL strings with tiny hashes, cutting payload size and locking down the API to a pre‑approved whitelist. This post shows a minimal Apollo Server + Client setup, the operational trade‑offs, and a verification checklist you can run today.
Persisted queries let a GraphQL server execute only pre-approved operations by hash. Here's how the APQ exchange works, when to move to a strict allow-list, and how to verify it.