Delivering Fast Experiences with AEMaaCS
summary
AEM as a Cloud Service sites use Fastly CDN and dispatcher headers to move load to the edge; one real migration shows cache hit ratio rising from ~5% to 96% cache hit ratio after fixing Cache-Control, max-age and response headers. Advice includes using conditional requests (ETag/Last-Modified), enabling stale-while-revalidate and surrogate-control for edge-only directives, avoiding high-cardinality Vary keys like user‑agent or cookies, and preferring dispatcher-set headers over per-request VCL. These changes reduce origin CPU load and eliminate simultaneous origin thundering.
AI-written summary · about
chapters (5)
- 0:00Introduction and agenda
- 2:29What is caching
- 8:12Checking cache metrics
- 9:16Cache optimization tips
- 28:49Q&A and closing
related talks
34mThe underappreciated power of content invalidation
01h 00mBuilding next gen composable services with Experience Manager
02mAEM Shorts: Modernizing Your AEM Implementation with Cloud Service
44mTop 10 Tips to Speed Up Your Adobe Experience Manager Site
25mCaching strategies on https://dev.to
28mEdge Caching Dynamic Rails Apps
47mCaching strategies on https://dev.to
17mShipping to the Edge