ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #apollographql
Configure Apollo Client's InMemoryCache with keyArgs:false and a merge function to append GraphQL connection pages without refetching the first page.
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.
When a mutation returns correct data but the UI shows stale or missing values, the cause is usually cache identity or typePolicies. Use this diagnostic guide to isolate the issue before adding refetches.
Learn how Apollo Federation stitches independent GraphQL services into a single schema, with a step‑by‑step example, common pitfalls, and verification tips.
Stop redundant network requests in your GraphQL app. Learn how Apollo Client's normalized cache flattens data and how to manage state updates without full page reloads.
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.
A decision guide for Apollo Client fetchPolicy: compare cache-first, network-only, cache-and-network, and no-cache against freshness, load, and offline needs.
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.
Learn how Apollo Client’s automatic cache normalization creates a single source of truth for GraphQL objects, preventing duplicate data and stale UI after mutations.
graphql
nodejs