Putting a cache infront of distributed redis cache

Question

I have a java enterprise application that does a lot of fetching of cached data. The data is stored in a 3 server redis cluster and is accessed by 5 backend api nodes.

I am seeing that we are putting alot of stress on the redis caches, which is why I am wondering if it is dumb to put a in-mem cache such as Ehcache in front of redis. With this solution I would set the TTL to be very short in the Ehcache.

Is this a common solution or is it more reasonable to look into expanding the redis cluster?

Using an integrated tool could make more sense, something like Geode/GemFire or InfiniSpan that take care of WAN/LAN (local/remote) replication for you. — mp911de
– mp911de, Commented Mar 12, 2018 at 14:34

alxg2112 · Accepted Answer · 2018-03-12 14:31:28Z

3

Thing you are talking about is called near cache. It's absolutely legit solution in some cases. It provides trade-off between performance and freshness of the values. However you can only consider this option if seeing a bit stale values is tolerable in your case. Just FYI, Apache Ignite supports this feature out of the box.

answered Mar 12, 2018 at 14:31

alxg2112

3182 silver badges11 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Putting a cache infront of distributed redis cache

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related