No more typing reviews! Try our Samantha, our new voice AI agent.

Hazelcast Platform vs Redis comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Hazelcast Platform
Ranking in In-Memory Data Store Services
7th
Average Rating
8.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
Redis
Ranking in In-Memory Data Store Services
1st
Average Rating
8.8
Reviews Sentiment
5.9
Number of Reviews
26
Ranking in other categories
NoSQL Databases (4th), Managed NoSQL Databases (6th), Vector Databases (4th), AI Software Development (13th)
 

Mindshare comparison

As of May 2026, in the In-Memory Data Store Services category, the mindshare of Hazelcast Platform is 10.6%, up from 2.5% compared to the previous year. The mindshare of Redis is 22.0%, up from 16.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
In-Memory Data Store Services Mindshare Distribution
ProductMindshare (%)
Redis22.0%
Hazelcast Platform10.6%
Other67.4%
In-Memory Data Store Services
 

Featured Reviews

PM
Director of Engineering at Visa
Distributed caching has reduced latency and now supports real-time stream processing
I think there are areas where Hazelcast Platform can improve, such as simplifying the cluster topology and sizing rules because they are still somewhat complex for someone new to Hazelcast. Understanding how the cluster topology forms and sizing rules work, such as partition balancing and traffic routing, should be much simpler. If one node has less RAM or a slightly slower CPU, it creates a cluster-wide performance bottleneck, which is critical, especially with transactional systems. Even though Hazelcast Platform has proven to be better, there can still be bottlenecks if the cluster topology and data partitioning are not easily understood. I also think that object handling and streamlined serialization should be prioritized; using standard Java serialization can be extremely slow. Providing native ultra-fast binary serialization out of the box, without requiring developers to write custom adapters, would be a significant improvement. It would be great if there were ready-to-use adapters for streamlined serialization and object handling.
Varuns Ug - PeerSpot reviewer
Senior software developer at Makemytrip
Caching has accelerated complex workflows and delivers low latency for high-traffic microservices
A few features of Redis that I use on a day-to-day basis and feel are among the best are extremely low latency and high throughput. Since Redis is in-memory, it makes it ideal for cases such as caching and rate limiting where response time is critical. TTL expiry support is very useful in Redis as it allows me to automatically evict stale data without manual cleanup, which is something I use heavily in my caching strategy. Another point I can mention is that the rich data structures such as strings, hashes, and even sorted sets are very powerful. I have used strings for caching responses and counters, whereas I have used hashes for storing structured objects. One more feature I can tell you about is atomic operations. Redis guarantees atomicity for operations such as incrementing a counter, which is very useful for rate limiting and avoiding race conditions in distributed systems. Finally, I want to emphasize that Redis is easy to scale and integrate, whether through clustering or using a distributed cache across microservices. Redis has impacted my organization positively by providing default support that is very useful. For metrics, in one of my core systems, introducing Redis as a distributed cache helped me achieve around an 80% cache hit rate, which reduced repeated downstream services. Real API latency also improved from around two seconds to approximately 450 milliseconds for P99. It also helped reduce the load on dependent services and databases, which improved overall system reliability.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"There have definitely been a lot more latency reductions and better SLA performance since using Hazelcast Platform, resulting in faster time to market overall for new features and capabilities because the architecture has become simpler."
"Redis has multiple valuable features such as being a free and reliable open-source tool."
"The performance of Redis is very fast."
"What I like best about Redis is its fast and easy use. It has interesting algorithms like HyperLogLog and provides useful features. It's also good for implementing scalable rate limiting."
"Since I started using Redis, I feel that the product is saving me some performance tuning time."
"Redis is a simple, powerful, and fast solution."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"I find Redis valuable primarily for its caching capabilities, particularly in handling cache requests effectively. Its simplicity in managing key-value pairs for caching is one of its strengths, making it a preferred choice over more complex databases like MongoDB for specific use cases. However, I haven't explored Redis extensively for managing complex data structures beyond caching, as MongoDB might be more suitable for such scenarios."
"Redis is good for distributed caching management."
 

Cons

"If one node has less RAM or a slightly slower CPU, it creates a cluster-wide performance bottleneck, which is critical, especially with transactional systems."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"For the PubSub feature, we had to create our own tools to monitor the events."
"There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient."
"I would prefer it if there was more information available about Redis. That would make it easier for new beginners. Currently, there is a lack of resources."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"In future releases, I would like Redis to provide its users with an option like schema validation. Currently, the solution lacks to offer such functionality."
"It's actually quite expensive."
 

Pricing and Cost Advice

Information not available
"Redis is an open-source solution. There are not any hidden fees."
"The tool is open-source. There are no additional costs."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is an open-source product."
"Redis is not an overpriced solution."
report
Use our free recommendation engine to learn which In-Memory Data Store Services solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
24%
Computer Software Company
10%
Comms Service Provider
7%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise6
Large Enterprise10
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about Redis?
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you u...
What needs improvement with Redis?
Overall, Redis is a powerful and reliable tool, but there are a few areas for improvement. One limitation is that Redis is memory-based, so scaling can become expensive compared to disk-based syste...
What is your primary use case for Redis?
My main use case for Redis is caching frequently accessed data to improve performance and reduce database load. For example, I cache API responses and user-related data so that repeated requests ca...
 

Also Known As

No data available
Redis Enterprise
 

Overview

 

Sample Customers

British Gas, Airbus Defense, Ellie Mae, Gamesys
1. Twitter 2. GitHub 3. StackOverflow 4. Pinterest 5. Snapchat 6. Craigslist 7. Digg 8. Weibo 9. Airbnb 10. Uber 11. Slack 12. Trello 13. Shopify 14. Coursera 15. Medium 16. Twitch 17. Foursquare 18. Meetup 19. Kickstarter 20. Docker 21. Heroku 22. Bitbucket 23. Groupon 24. Flipboard 25. SoundCloud 26. BuzzFeed 27. Disqus 28. The New York Times 29. Walmart 30. Nike 31. Sony 32. Philips
Find out what your peers are saying about Redis, Amazon Web Services (AWS), Google and others in In-Memory Data Store Services. Updated: April 2026.
893,221 professionals have used our research since 2012.