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 (10th)
Redis
Average Rating
8.8
Reviews Sentiment
5.9
Number of Reviews
26
Ranking in other categories
NoSQL Databases (4th), Managed NoSQL Databases (5th), In-Memory Data Store Services (1st), Vector Databases (4th), AI Software Development (12th)
 

Featured Reviews

Ismail El-Dahshan - PeerSpot reviewer
CEO at areebah
Easy to set up with good support and good routing scenarios
The triggering and the events that they have triggered as well as the route of the message according to the events are very useful. The triggering scenarios and routing scenarios are all good. It's a very useful solution for financial institutions. The initial setup is pretty straightforward. The stability has been good. I've found the product to be scalable. Technical support is responsive.
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

"The triggering scenarios and routing scenarios are all good, making it a very useful solution for financial institutions."
"I'm an administrator, and what I like most is the interface, the security, and the storage."
"The stability has been good."
"The system efficiently processes and calculates the data flow within the cluster using DLP functionality."
"I am happy with the product, other than pricing I don't have any other improvements that I can suggest."
"The performance of Redis is very fast."
"It is particularly efficient for cloud-based storage and operations."
"Redis is a simple service that does what it promises."
"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."
"Redis acts as an in-memory search tool that improves the speed of operations."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"The ability to fetch and save data quickly is valuable."
"Redis is good for distributed caching management."
 

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."
"In the next release, I would like to see the GUI allow you to configure the security section."
"The pricing needs to be improved."
"The product's interface needs improvement."
"It would be helpful if they could help us explain why they, as in, the customers, should use the product and the overall benefits."
"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."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"One limitation is that Redis is memory-based, so scaling can become expensive compared to disk-based systems."
"Redis presents a single point of failure and lacks fault tolerance."
"Redis should have an option to operate without Docker on a local PC."
"For the PubSub feature, we had to create our own tools to monitor the events."
"Managing memory efficiently and troubleshooting issues can sometimes require additional tooling, so these areas can also be improved."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
 

Pricing and Cost Advice

"The platform is averagely priced."
"The pricing needs to be improved."
"Redis is not an overpriced solution."
"Redis is an open-source product."
"Redis is an open-source solution. There are not any hidden fees."
"We saw an ROI. It made the processing of our transactions faster."
"The tool is open-source. There are no additional costs."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
886,906 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 Enterprise9
 

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...
 

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 Event Streams vs. Redis and other solutions. Updated: April 2026.
886,906 professionals have used our research since 2012.