Caches are sexy. They are a one-night stand. We need to avoid them in a long-term relationship.
TL;DR: Any junior student can create a cache. Almost no senior developer can debug and invalidate them.
Lack of transparency
If you have a conclusive benchmark and are willing to pay for some coupling: Put an object in the middle.
Unit test all your invalidation scenarios. Experience shows we face them in an incremental way.
Look for a real world cache metaphor and model it.
This is a design smell.
It will be difficult to enforce by policy.
- Premature Optimization
Caches should be functional and intelligent
In this way we can manage invalidation.
General purpose caches are suitable only for low level objects like operating systems, files and streams.
We shouldn't cache domain objects.
This page is hosted on a cached website.
There are only two hard things in Computer Science: cache invalidation and naming things.
This article is part of the CodeSmell Series.