This document summarizes a presentation on content invalidation strategies for Apache Sling and content delivery networks (CDNs). It discusses different layers of caching from the content management system to the browser. It also covers various invalidation models and techniques for invalidating specific resources, related resources, and entire sections of cached content. Specific examples are provided for invalidating digital asset management assets, vanity URLs, reusable components, and browser caches. The importance of precise invalidation and planning for inclusion are emphasized.
08448380779 Call Girls In Greater Kailash - I Women Seeking Men
The underappreciated power of content invalidation
1. APACHE SLING & FRIENDS TECH MEETUP
10-12 SEPTEMBER 2018
The underappreciated power of content invalidation
Jakub Wądołowski, Cognifide (@jwadolowski)
14. The plan
14
▪ High hit ratio & cache coverage
▪ Long TTLs (30+ days)
▪ AEM content changes reflected quickly
▪ Precise invalidation
https://flic.kr/p/7F4bHa
33. Reusable components
33
▪ Common elements (i.e. header)
▪ SDI (Sling Dynamic Include) to the rescue
▪ SSI (Server Side Includes)
▪ ESI (Edge Side Includes)
https://flic.kr/p/dgghVK
36. Tag-based invalidation (1/4)
36
▪ Not everything can be wrapped into SSI/ESI
▪ Layout/templates
▪ HTML markup configs
▪ Is QueryBuilder the only option?
https://flic.kr/p/25LNnfK
45. We barely scratched the surface…
45
▪ API throttling
▪ Error handling
▪ Payload limits
▪ Non-obvious content references
https://flic.kr/p/pSB1rM
46. Lessons learned
46
▪ purge all is dangerous
▪ make invalidation as precise as possible
▪ plan SSI/ESI since the very beginning
▪ QueryBuilder calls may require extra indexes
https://flic.kr/p/dgge8U