Update on my blog about Hybris.
I’ve added a smart caching mechanism for page fragments in hybris. Each fragment has a composite key that reflects its dependencies. For example, to cache the list of delivery addresses for an online store (I have a video example), the composite key might be the user identifier – this way, different caches will be used for different users.
This mechanism is particularly effective if “heavy” features (in terms of memory and processor usage) are moved from page controllers to components, as the described technique is not perfectly suited for caching page controllers.
To better understand the idea, it’s easiest to look at the template screenshots in the middle of the article.

