The underappreciated power of content invalidation
summary
A complex multi‑AEM setup adopts an “everything is cacheable” policy and finds cache invalidation is the real problem: dispatcher scripts compute short customer URLs, call CDN APIs (Akamai APIs vary wildly — older calls take minutes, newer ones seconds), and must invalidate all asset renditions and pages that reference an asset (alt text requires page invalidation). Use query‑builder to find references, avoid global purge, prefer Sling Dynamic Include or edge includes for shared fragments, and rely on surrogate key tagging with CDN tag APIs (Fastly style) instead of stop files.
AI-written summary · about
chapters (7)
- 0:00Introduction to content invalidation
- 3:35HTTP caching fundamentals
- 10:33Dispatcher invalidation techniques
- 17:42CDN invalidation strategies
- 24:18Browser caching complexities
- 30:20Lessons learned and best practices
- 32:41Q&A session
related talks
29mDelivering Fast Experiences with AEMaaCS
23mContent delivery sucks, and what you can do about it
10mEnhancing CDN Performance and Cutting Egress Costs in Large Video Libraries
19mA/B User Testing When Your CDN Cache Messes With Your Results
29mLove your cache: Optimize for the second load
28mUnderstand GraphQL API performance options and query optimizations
42mCaching for Cash
21mHigh Performance APIs through Caching