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
5th
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 (3rd), Managed NoSQL Databases (6th), Vector Databases (2nd), AI Software Development (12th)
 

Mindshare comparison

As of June 2026, in the In-Memory Data Store Services category, the mindshare of Hazelcast Platform is 10.7%, up from 2.9% compared to the previous year. The mindshare of Redis is 21.6%, up from 17.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
In-Memory Data Store Services Mindshare Distribution
ProductMindshare (%)
Redis21.6%
Hazelcast Platform10.7%
Other67.7%
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 NIT
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 is a powerful and reliable tool for improving application performance."
"Redis is a simple, powerful, and fast solution."
"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."
"Redis acts as an in-memory search tool that improves the speed of operations, allowing for quicker data retrieval and enhancing the performance of applications."
"Overall, my experience with Redis has been very positive, and it has played a key role in improving performance, scalability, and system responsiveness in our back-end system."
"The solution is fast, provides good performance, and is not too expensive."
"Redis is a simple service that does what it promises."
"The best thing about Redis is its ability to handle large amounts of data without frequently hitting the database. You can store data in temporary memory, especially for high-volume data."
 

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."
"If we use a lot of data, it will eventually cost us a lot."
"There are some points where I feel Redis can be improved."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly."
"Redis should have an option to operate without Docker on a local PC."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"There is a lack of documentation on the scalability of the solution."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
24%
Computer Software Company
10%
University
6%
Comms Service Provider
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

What needs improvement with Hazelcast Platform?
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. Underst...
What is your primary use case for Hazelcast Platform?
My main use case for Hazelcast Platform is to build distributed cache systems across different services that we have. The biggest use is the caching. Additionally, from time to time, we use this fo...
What advice do you have for others considering Hazelcast Platform?
My advice for others looking into using Hazelcast Platform is to study the architecture and data modeling thoroughly. Choosing the right topology for the application or platform is crucial when usi...
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...
What advice do you have for others considering Redis?
My main advice for those looking into using Redis is to focus on the use case; Redis excels where low latency is critical, such as caching, session management, or real-time features, rather than us...
 

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: May 2026.
900,644 professionals have used our research since 2012.