Skip to content
Networking·Advanced·Conceptual·1 min read

How does a GraphQL client typically avoid re-fetching data it already has?

Short interview answer

A normalized client cache such as Apollo or Relay stores entities by type and id, so a query for a record already in the cache can be served instantly and merged as new fields arrive.

Key takeaway

Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.

← Back to REST, GraphQL, and WebSockets

Related questions