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

IBM Event Streams vs Redis comparison

 

Comparison Buyer's Guide

Executive Summary

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

IBM Event Streams
Average Rating
8.4
Reviews Sentiment
7.8
Number of Reviews
3
Ranking in other categories
Message Queue (MQ) Software (13th)
Redis
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
28
Ranking in other categories
NoSQL Databases (3rd), Managed NoSQL Databases (6th), In-Memory Data Store Services (1st), Vector Databases (3rd), AI Software Development (9th)
 

Featured Reviews

TM
IBM MQ Specialist / Administrator at a financial services firm with 10,001+ employees
Easy to use, stable, has a good interface, and the security is good
I don't know if it's because of experience, but for me, it was easy to install. It's just a matter of having an RPM, then click next, next, and next again. The difficult part comes in when you have to configure the security. That is the most difficult part, but it's not that difficult. It takes less than two hours to install. Two hours max, because I did one yesterday. I installed it on AWS and it was easy to install the software. It was less than an hour for the bare minimum installation. Setting up the security, took close to two hours.
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

"The stability has been good."
"I'm an administrator, and what I like most is the interface, the security, and the storage."
"The system efficiently processes and calculates the data flow within the cluster using DLP functionality."
"The triggering scenarios and routing scenarios are all good, making it a very useful solution for financial institutions."
"I am happy with the product, other than pricing I don't have any other improvements that I can suggest."
"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 use Redis efficiently."
"The performance of Redis is very fast."
"Redis has had a positive impact by improving application performance, reducing database load, and making the system more scalable."
"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."
"I use Redis mostly to cache repeated data that is required."
"Overall, I want to say that Redis truly adds value, especially for low latency and high throughput use cases."
"Redis is a simple, powerful, and fast solution."
"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."
 

Cons

"It would be helpful if they could help us explain why they, as in, the customers, should use the product and the overall benefits."
"The product's interface needs improvement."
"In the next release, I would like to see the GUI allow you to configure the security section."
"The pricing needs to be improved."
"There are some points where I feel Redis can be improved."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"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."
"If we use a lot of data, it will eventually cost us a lot."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"There is a lack of documentation on the scalability of the solution."
"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."
"Making management easier, especially for teams operating large Redis clusters, would be helpful."
 

Pricing and Cost Advice

"The platform is averagely priced."
"The pricing needs to be improved."
"The tool is open-source. There are no additional costs."
"Redis is an open-source solution. There are not any hidden fees."
"Redis is not an overpriced solution."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is an open-source product."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
904,928 professionals have used our research since 2012.
 

Top Industries

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

Company Size

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

Questions from the Community

Ask a question
Earn 20 points
What needs improvement with Redis?
I have faced a few challenges and limitations with Redis. Although it is extremely powerful, there are challenges and areas for improvement depending on the use case. The first challenge is memory ...
What is your primary use case for Redis?
The main use case for Redis is caching. Caching is the primary purpose of using Redis for my organization, as I use it to cache frequently accessed data to improve application performance and reduc...
What advice do you have for others considering Redis?
If somebody is looking to use Redis, it is much easier and more scalable for making most database queries faster, especially for repeated pages while fetching data. It helps tremendously in handlin...
 

Comparisons

 

Also Known As

No data available
Redis Enterprise
 

Overview

 

Sample Customers

American Airlines, UBank, Bitly, Eurobits, Active International, Bison, Contextor, Constance Hotels, Resorts & Golf, Creval, Deloitte, ExxonMobil, FaceMe, FacePhi, Fitzsoft, Fuga Technologies, Guardio, Honeywell, Japanese airline, Jenzabar, KONE
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 IBM, Apache, Amazon Web Services (AWS) and others in Message Queue (MQ) Software. Updated: July 2026.
904,928 professionals have used our research since 2012.