Enlist the Help of Your Schema for Caching!
summary
Based on GraphCDN operational experience the talk gives concrete schema rules that materially improve caching: prefer id or _id fields and configure them as key fields so normalized clients (Apollo, Relay) and GraphCDN find and purge objects; enforce globally unique IDs like UUIDs; avoid duplicate types and instead add transient metadata via the cursor connection pattern; make a schema-aware cache to enable partial results and fragment handling; and when using document caches split queries into public and private so shared responses are reusable.
AI-written summary · about
chapters (4)
related talks
24mGraphQL Clients
25mGraphQL and caching - Why is it so hard, or is it? 
08mFine-tuning Apollo Client's normalized cache
26mCache Strategies with Best Practices
23mHow to edge cache GraphQL APIs
21mCaching your GraphQL data graph
20mThe Apollo Cache is Your Friend, if You Get To Know It
37mCaching Deep Dive: The Ultimate Way To Speed up Your GraphQL API