Choosing Between Persisted Query Hashing and Dynamic Queries in Apollo Server
Decide between persisted query hashing and dynamic queries in Apollo Server to optimize for latency, security, and developer velocity.
Loading…
ReadMeFeed / Community knowledge
GraphQL
Real questions. Useful conversations. Find the people who know your stack.
GraphQL
Languages & runtimes · #graphql
Fetching LeetCode Problems Without Skipping or Repeating Pages
LeetCode's problem list uses offset-based pagination, which can skip or repeat items when the list changes. Track a client-side cursor instead of trusting page numbers.
leetcodeKeep Apollo Client Cache in Sync After a Mutation Without Refetching
Use a cache update function with Apollo Client InMemoryCache to merge mutation results locally and avoid unnecessary refetches. Includes verification steps and limits.
apollographqlUsing GraphQL Persisted Queries to Shrink Requests and Allow-List Operations
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.
Configure Apollo Client InMemoryCache Field Policies for Paginated Queries
Learn how to set Apollo Client InMemoryCache field policies for offset/limit and cursor-based pagination so fetchMore merges pages correctly without duplicates.
Cut GraphQL Payloads with Persisted Queries in Apollo Client and Server
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.
Why Gatsby's Unified GraphQL Layer Changes How You Think About Content
Gatsby's unified GraphQL layer shifts all data fetching to build time, turning heterogeneous content sources into a single compile-time validated schema. Here's how it works, where it strains, and a minimal example you can verify today.
gatsbyMerge paginated GraphQL pages in Apollo Client 3
Configure Apollo Client 3's InMemoryCache to merge paginated GraphQL pages instead of replacing them, with fetch-policy trade-offs and verification steps.
Shrink GraphQL Requests with Automatic Persisted Queries
Send query hashes instead of full GraphQL documents on repeat requests to save bandwidth and improve cache hits.