Redis or Ehcache?

Sachin Sharma picture Sachin Sharma · Oct 14, 2015 · Viewed 24.7k times · Source

Which is better suited for the following environment:

  1. Persistence not a compulsion.
  2. Multiple servers (with Ehcache some cache sync must be required).
  3. Infrequent writes and frequent reads.
  4. Relatively small database (very less memory requirement).

I will pour out what's in my head currently. I may be wrong about these.

I know Redis requires a separate server (?) and Ehcache provides local cache so it must be faster but will replicate cache across servers (?). Updating all caches after some update on one is possible with Ehcache.

My question is which will suit better for the environment I mentioned?
Whose performance will be better or what are scenarios when one may outperform another?

Thanks in advance.

Answer

smallufo picture smallufo · Oct 15, 2015

You can think Redis as a shared data structure, while Ehcache is a memory block storing serialized data objects. This is the main difference.

Redis as a shared data structure means you can put some predefined data structure (such as String, List, Set etc) in one language and retrieve it in another language. This is useful if your project is multilingual, for example: Java the backend side , and PHP the front side. You can use Redis for a shared cache. But it can only store predefined data structure, you cannot insert any Java objects you want.

If your project is only Java, i.e. not multilingual, Ehcache is a convenient solution.