Apache Ignite vs redis cluster(use partition) vs other solution

moon picture moon · Jan 30, 2017 · Viewed 13.3k times · Source

Hi I looking for In memory data grid or similar one.

My use case.

  1. Data griding in memory. scale out available.
  2. backup node available.
  3. persistent backup available.
  4. (optional) free or opensource solution

I did googling and I found candidates below
- Apache Ignite
- Redis cluster
- Hazelcast(community)

I prefer Ignite to Hazelcast because, Ignite support use direct buffer.

But I don't know Redis cluster partitioning whether it is stable or not. and, I don't know if apache ignite performance better than redis cluster or not.

Apache Ignite comparable to redis cluster? or impropert comparison? Thanks for your answer

Answer

Nikita Koksharov picture Nikita Koksharov · May 4, 2017

But I don't know Redis cluster partitioning whether it is stable or not

Redis cluster feature is stable since 3.x version and used in production by many companies.

Apache Ignite comparable to redis cluster? or impropert comparison?

Comparison Apache Ignite vs Redis only is wrong, because these projects have different grade. Redis is positioned as a storage and not as a Data Grid like Apache Ignite. So for proper comparison Apache Ignite should be compared vs Redisson - Redis Java Client with features of In-Memory Data Grid. It offers the same features as Apache Ignite.

Redisson supports fully managed Redis services like AWS Elasticache, Azure Redis Cache. You don't need to manage/deploy/maintain Redis cluster by yourself of hire devops to do this. Apache Ignite doesn't offer such feature and you should manage/deploy/maintain it by yourself.