Try our new research platform with insights from 80,000+ expert users

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.7
Number of Reviews
24
Ranking in other categories
NoSQL Databases (5th), Managed NoSQL Databases (7th), In-Memory Data Store Services (1st), Vector Databases (3rd), AI Software Development (14th)
 

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.
RK
SDE 1 at ValueMomentum
Caching and session design has improved performance and now supports high-traffic workloads
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 systems. While it offers persistence options, it is not always ideal for large datasets where cost efficiency is critical. Another area is cache consistency; Redis itself does not enforce consistency with the primary database, so developers need to carefully design cache invalidation strategies. More built-in mechanisms or patterns to simplify this would be helpful. Additional areas where Redis could improve include monitoring, security, and ease of use in large-scale ecosystems. From a monitoring perspective, while Redis provides basic metrics, deep visibility into issues such as memory fragmentation, hot keys, or latency spikes often requires external tools; more built-in, user-friendly options would make diagnosing production issues quicker. Regarding security, Redis has improved over time, but historically, it required careful configurations; features such as authentication and encryption exist but are not always enabled by default, posing a risk if not properly set up. A strong, secure by default configuration would be beneficial. In terms of ease of use, while Redis is straightforward for basic use cases, managing clusters and persistence strategies can become complex at scale, so better abstractions or tooling for distributed setups and operations would make it more developer-friendly.

Quotes from Members

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

Pros

"I am happy with the product, other than pricing I don't have any other improvements that I can suggest."
"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."
"The triggering scenarios and routing scenarios are all good, making it a very useful solution for financial institutions."
"Redis is a simple service that does what it promises."
"Redis is a simple, powerful, and fast solution."
"Redis acts as an in-memory search tool that improves the speed of operations."
"The performance of Redis is very 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."
"The in-memory data makes it fast."
"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."
"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."
 

Cons

"In the next release, I would like to see the GUI allow you to configure the security section."
"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."
"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 pricing needs to be improved."
"One limitation is that Redis is memory-based, so scaling can become expensive compared to disk-based systems."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"There is a lack of documentation on the scalability of the solution."
"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."
"Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
 

Pricing and Cost Advice

"The pricing needs to be improved."
"The platform is averagely priced."
"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."
"Redis is an open-source product."
"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.
885,286 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 Enterprise4
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?
The disadvantage of Redis is that it's a little bit hard to have too many clusters or too many nodes and create the clusters. The sync between the nodes is easier to implement with Couchbase, for e...
What is your primary use case for Redis?
Redis is used for a part of a booking engine for travel, specifically for the front part to get some sessions and information about the sessions. If a customer or user is using the sites in differe...
 

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: March 2026.
885,286 professionals have used our research since 2012.