GraphQL Clients
summary
Explains why GraphQL lets clients build caches automatically by using __typename plus id so responses normalize into storable objects and avoid repeated requests, contrasts resource caching (query or URL keys) with object caching (per-ID storage), describes how Apollo uses query hashes and completeness checks and how Relay-compatible APIs with a node route enable automatic reuse and updates, and proposes schema annotations and compiled cache libraries that drive automatic invalidation and mutation-driven list updates.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:28Terminology
- 2:25Why cache
- 2:57Perfect cache librarian
- 4:24Invalidation
- 4:52Resource Cache
- 6:59Oracle
- 7:29Object Cache
- 8:44Manual Object Cache
- 10:02Type Name
- 10:33GraphQL Curl
- 11:03GraphQL Routes
- 11:52Problems with GraphQL Routes
- 12:48GraphQL Knowledge
- 14:30Relay
- 16:55Restrictions
- 20:42Automatic updates
- 21:59GraphQL is introspective
- 22:56GraphQL has firstclass introspection
related talks
25mDemystifying GraphQL Clients
25mGraphQL and caching - Why is it so hard, or is it? 
08mFine-tuning Apollo Client's normalized cache
21mCaching your GraphQL data graph
29mWrite Queries, Not Code
58mGraphQL -- Flexible APIs for Adaptive Clients
06mEnlist the Help of Your Schema for Caching!
24mBuilding Reactive GraphQL Apps With Apollo