Fine-tuning Apollo Client's normalized cache
summary
Explains how Apollo Client’s normalized cache stores a deduplicated lookup table of objects keyed by __typename + ID or custom keyFields, shows fetch policies (cache-first, cache-and-network, network-only) and when automatic merges happen versus when manual update functions are required, demonstrates eviction and garbage collection APIs with concrete cache-size changes (212 → 419 items) after a query, and shows that IDs plus stable keys are required for predictable UI updates.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:39Split data into individual objects
- 2:11Assigning unique identifiers
- 2:53Put the objects into a flattened data structure
- 5:34Garbage Collection & Eviction
related talks
20mThe Apollo Cache is Your Friend, if You Get To Know It
24mGraphQL Clients
21mCaching your GraphQL data graph
31mDeep Dive into Apollo Client
16mLightning Talk: Next-Generation GraphQL Cache Management in Your Android and iOS Apps
20mCaching your data graph with Apollo Kotlin
06mEnlist the Help of Your Schema for Caching!
23mHow to Edge Cache GraphQL APIs