Need advice about which tool to choose?Ask the StackShare community!
Hazelcast vs Redis: What are the differences?
Hazelcast: Clustering and highly scalable data distribution platform for Java. With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution; Redis: An in-memory database that persists on disk. Redis is an open source, BSD licensed, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.
Hazelcast and Redis belong to "In-Memory Databases" category of the tech stack.
"High Availibility" is the primary reason why developers consider Hazelcast over the competitors, whereas "Performance" was stated as the key factor in picking Redis.
Hazelcast and Redis are both open source tools. Redis with 37.1K GitHub stars and 14.3K forks on GitHub appears to be more popular than Hazelcast with 3.15K GitHub stars and 1.15K GitHub forks.
reddit, Instacart, and Slack are some of the popular companies that use Redis, whereas Hazelcast is used by Yammer, Seat Pagine Gialle, and Stormpath. Redis has a broader approval, being mentioned in 3239 company stacks & 1732 developers stacks; compared to Hazelcast, which is listed in 25 company stacks and 15 developer stacks.
Pros of Hazelcast
- High Availibility10
- Distributed Locking6
- Distributed compute5
- Sharding5
- Load balancing4
- Sql query support in cluster wide3
- Map-reduce functionality3
- Written in java. runs on jvm3
- Publish-subscribe3
- Performance2
- Simple-to-use2
- Multiple client language support2
- Rest interface2
- Optimis locking for map2
- Super Fast1
- Admin Interface (Management Center)1
- Better Documentation1
- Easy to use1
Pros of Redis
- Performance879
- Super fast536
- Ease of use511
- In-memory cache441
- Advanced key-value cache321
- Open source190
- Easy to deploy179
- Stable163
- Free152
- Fast120
- High-Performance40
- High Availability39
- Data Structures34
- Very Scalable32
- Replication23
- Great community20
- Pub/Sub19
- "NoSQL" key-value data store17
- Hashes14
- Sets12
- Sorted Sets10
- Lists9
- BSD licensed8
- NoSQL8
- Async replication7
- Integrates super easy with Sidekiq for Rails background7
- Bitmaps7
- Open Source6
- Keys with a limited time-to-live6
- Strings5
- Lua scripting5
- Awesomeness for Free!4
- Hyperloglogs4
- outstanding performance3
- Runs server side LUA3
- Networked3
- LRU eviction of keys3
- Written in ANSI C3
- Feature Rich3
- Transactions3
- Data structure server2
- Performance & ease of use2
- Existing Laravel Integration1
- Automatic failover1
- Easy to use1
- Object [key/value] size each 500 MB1
- Simple1
- Channels concept1
- Scalable1
- Temporarily kept on disk1
- Dont save data if no subscribers are found1
- Jk0
Sign up to add or upvote prosMake informed product decisions
Cons of Hazelcast
- License needed for SSL3
Cons of Redis
- Cannot query objects directly14
- No secondary indexes for non-numeric data types2
- No WAL1
Sign up to add or upvote consMake informed product decisions
What is Hazelcast?
What is Redis?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Hazelcast?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Hazelcast?
What tools integrate with Redis?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+9
+8
+17
+9
+12+23+17