Understand GraphQL API performance options and query optimizations
summary
AEM GraphQL supports persisted queries (created via PUT, executed via GET) whose URL-parameterized variables are encoded after a semicolon and whose results CDN-cache with configurable headers like max-age, stale-while-revalidate and stale-if-error. AEM uses hybrid filtering that maps top-level filters to JCR and applies remaining filters in-memory, so upgrading content fragments via Cloud Manager enables new filter optimizations. Scale numbers: ~11.5 billion Cloud calls and 34 million AMS calls over two weeks. Paging supports offset and cursor-based pagination (forward only); pre-release enables Dynamic media _dynamicUrl renditions generated on first access.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:43GraphQL API
- 1:07Multiple configurations
- 2:07Persistent queries
- 3:04GraphQL API usage
- 3:43Finetuning GraphQL queries
- 4:58How to prepare for GraphQL optimizations
- 5:33Hybrid filtering
- 6:27Filtering with variables
- 7:50Offsetbased paging
- 8:19Cursorbased paging
- 9:03Sorting GraphQL results
- 9:35Dynamic image delivery
- 10:48Best practices
- 12:02Dynamic fields
- 13:11Persistence queries
- 14:31Combining features
- 14:57Sample queries
- 22:55What about AM65
- 23:32Recap
- 24:02Questions
related talks
12mImprove Application Performance and User Engagement with Advanced GraphQL Features
32mHeadless Adobe Experience Manager Sites
37mCaching Deep Dive: The Ultimate Way To Speed up Your GraphQL API
25mOptimizing GraphQL Applications
23mDelivering commerce experiences at scale
23mHow to edge cache GraphQL APIs
24mHow to cache GraphQL queries at the edge
26mBuild a performance-optimized GraphQL API