Caffeine and HttpCachestore

Question

Hi all
 
   I am trying to understand the drawbacks and benefits of using Caffeine In-Memory Caching. I saw ACS provides Http Cache Store using same mechanism . If you have used in your projects , could you help me understand what were the benefits and major challenges you faced ? Any drawbacks of using !? What kind of JSON can be stored mostly !? ( I understand it should be static , but I would still love to hear if anyone has used it for JSON related to products for ecommerce website etc) 
 
What should be the caching strategy and how frequent should we flush the cache ? Since it is in-memory cache , how should we use mechanism efficiently !?
 
Thanks
Veena

arunpatidar · Accepted Answer

Hi @veenavikraman

We're using Guava for in-memory caching to store e-commerce data.

The main challenge I see is with cache invalidation—when the catalog is updated, we need to ensure the latest product info is shown. While you can use TTL for the in-memory cache, things get trickier with multiple layers.

We’re also using TTL-based in-memory cache alongside dispatcher and CDN caching, all tied into a complex auto-invalidation solution that can easily turn into a nightmare!

https://medium.com/@giuseppebaglio/automating-cdn-cache-invalidation-in-aem-d419b538c8ea

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded