What are the most effective caching strategies for Experience Fragments in AEM, and how can I ensure seamless updates to cached pages referencing shared content? I've come across various approaches mentioned in a blog, but I'd like to hear from the community about their experiences and recommendations.
Hello @aem101
The approach that is followed depends on:
- How frequent XF updates are?
- How much cache is affected by these updates?
- What is the caching strategy for the site?
You might also notice a difference in behaviour of XF when it is added as part of template (like header) or page (like contributor XF in WKND).
- In case of contributor XF, publishing the referenced pages would only affect them (a smaller set). Its the OOTB behaviour now, that all pages referencing the published XF will also be updated.
- In case of header XF, it affects the entire site. In this case, one might even turn off the entire site flush and let ttls update site. This is discussed in blog.
- If there is a use-case, where an XF update is frequent and affects a large set of pages, an SDI approach for such XF will make sense.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.