redis vs hazelcast [closed]

Question

Redis Vs Hazelcast If my app:

• Have a lot of http requests (6,000 per minute, I collect clicks info) that needs to be saved
• Have a lot of http requests that query the data previously saved.

My Questions are - Which one between Redis and Hazelcast should I chose to store and query data - which one is faster for reads and writes? - which one is more reliable? - Might Cassandra be a better option?

Answering any of the questions helps

Answer 1

We switched from redis to hazelcast for our caching needs.

• Protostuff + Hazelcast is much faster for us than
• Protostuff + Jedis (pooled) + Redis

We use protostuff to serialize beans that are expensive to create. Hazelcasts standard-serialization mechanism is much slower. Our environment is Glassfish 3.1.

Hazelcast looks like they only have java libs, Redis has one for every language.

True. Hazelcast provides just a REST API and an implementation of the memcached protocol.

Answer 2

There is a very handy lib - Redisson. It provides distributed Java objects and services (BitSet, BloomFilter, Set, SortedSet, Map, ConcurrentMap, List, Queue, Deque, BlockingQueue, BlockingDeque, ReadWriteLock, Semaphore, Lock, AtomicLong, CountDownLatch, Publish / Subscribe, RemoteService, ExecutorService, LiveObjectService, ScheduledExecutorService) on top of Redis server!

It supports cluster, sentinel, master/slave and single connection modes.

Perfectly works in cloud and supports AWS Elasticache and Azure Redis Cloud

Below are some success stories from Redisson customers:

Moving from Hazelcast to Redis
Distributed Locking with Redis (Migration from Hazelcast)

Please note: I'm an author of Redisson