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

IBM MQ 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 MQ
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
164
Ranking in other categories
Business Activity Monitoring (1st), Message Queue (MQ) Software (1st), Message Oriented Middleware (MOM) (1st)
Redis
Average Rating
8.8
Reviews Sentiment
8.0
Number of Reviews
22
Ranking in other categories
NoSQL Databases (7th), In-Memory Data Store Services (1st), Vector Databases (4th)
 

Featured Reviews

SelvaKumar4 - PeerSpot reviewer
Offers the ability to batch metadata transfers between systems that support MQ as the communication method
We find it scalable for internal applications, but not so much for external integrations. It should support a wider range of protocols, not just a few specific ones. Many other products have broader protocol support, and IBM MQ is lagging in that area. IBM MQ needs to improve the UI for quicker logging. Users should also have a lot more control over logging, with a dashboard-like interface. That's something they should definitely work on.
Yaseer Arafat - PeerSpot reviewer
Unmatched Performance and Scalability for Modern Applications
Redis has room for improvement in a few areas. Enhanced tools for managing and monitoring clusters would be beneficial, as would built-in security mechanisms like advanced encryption and granular access controls. Simplifying setup and configuration could make Redis more accessible to new users. Introducing more enterprise-grade features, such as better multi-tenancy support and improved backup and restore capabilities, would also be advantageous. For the next release, it would be great to see enhanced cluster management tools, native multi-region supports for better data redundancy, integrated analytics for deeper insights, AI and ML integration features, and improved developer experience through enhanced SDKs and tools.

Quotes from Members

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

Pros

"The solution is fast with end data compared to other messaging tools."
"Secure, safe, and very fast."
"Combined with IBM MQ, this product is our primary data store."
"We use our routing feature when the request is coming from the business application. The request goes to the distributive side and it is routed to the right claim instance."
"The solution allows one to easily configure an IBM MQQueueManager."
"I have found that the solution scales well."
"The message queue and the integration with any development platform/language, i.e., NET and Java, are the most valuable features."
"The usability of the solution is very good."
"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."
"The solution is fast, provides good performance, and is not too expensive."
"The online interface is very fast and easy to use."
"Redis has multiple valuable features such as being a free and reliable open-source tool."
"The in-memory data makes it fast."
"Redis is good for distributed caching management."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"Redis acts as an in-memory search tool that improves the speed of operations."
 

Cons

"There are things within the actual product itself that can be improved, such as limitations on message length, size, etc. There is no standardized message length outside of IBM. Each of the implementations of the MQ series or support of that functionality varies between various suppliers, and because of that, it is very difficult to move from one to the other. We have IBM MQ, but we couldn't use it because the platform that was speaking to MQ didn't support the message length that was standard within IBM MQ. So, we had to use a different product to do exactly the same thing. So, perhaps, there could be more flexibility in the standards around the message queue. If we had been able to increase the message queue size within the IBM MQ implementation, we wouldn't have had to go over to another competing product because the system that was using MQ messaging required the ability to hold messages that were far larger than the IBM MQ standard. So, there could be a bit more flexibility in the structuring. It has as such nothing to do with the IBM implementation of MQ. It is just that the standard that is being put out onto the market doesn't actually stipulate those types of things."
"The pricing needs improvement."
"While there is support for API, it's not like the modern API capabilities."
"It could get a face lift with a modern marketing campaign."
"I would just like a more user-friendly experience to do common administration tasks. I know that you can use MQ Explorer, but having something that's already built in would definitely be useful."
"The installation of product upgrades and patches is very difficult. It requires the use of the IBM Installation Manager (IM)."
"We need to have a better administration console and better monitoring features. Right now, they are not good and could be a lot better."
"In the next release, I would like for there to be easier monitoring. The UI should be easier for non-technical users to set up appliances and servers."
"It's actually quite expensive."
"The solution's pricing for a local installation is very expensive."
"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."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
"Redis should have an option to operate without Docker on a local PC."
"There is a lack of documentation on the scalability of the solution."
"Redis presents a single point of failure and lacks fault tolerance."
 

Pricing and Cost Advice

"It is a very expensive product compared to the open source products in the market."
"In terms of cost, IBM MQ is slightly on the higher side."
"Our costs haven't increased but they also have not improved."
"The fee for this solution is on the higher end of the scale."
"This solution requires a license and we have purchased an enterprise license."
"The price of the solution could be reduced, and we are on an annual subscription."
"To implement such an IBM solution, a company has to pay a lot in term of licensing and consultancy. A pricing model might be a better option."
"Most of our customers are quite happy with the solution but they have an issue with the cost. They want to move to cheaper solutions."
"Redis is an open-source solution. There are not any hidden fees."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is an open-source product."
"Redis is not an overpriced solution."
"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.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
38%
Computer Software Company
12%
Manufacturing Company
6%
Government
5%
Financial Services Firm
22%
Computer Software Company
15%
Educational Organization
7%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What is MQ software?
Hi As someone with 45+ years of experience in the Transaction and Message Processing world, I have seen many "MQ" solutions that have come into the market place. From my perspective, while each pro...
What are the differences between Apache Kafka and IBM MQ?
Apache Kafka is open source and can be used for free. It has very good log management and has a way to store the data used for analytics. Apache Kafka is very good if you have a high number of user...
How does IBM MQ compare with VMware RabbitMQ?
IBM MQ has a great reputation behind it, and this solution is very robust with great stability. It is easy to use, simple to configure and integrates well with our enterprise ecosystem and protocol...
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?
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. Additionally, better documentation is neede...
What is your primary use case for Redis?
My primary use case for Redis has been leveraging it as a high-performance, in-memory data store to support real-time features in web applications. For instance, I used Redis to manage live chat sy...
 

Comparisons

 

Also Known As

WebSphere MQ
Redis Enterprise
 

Overview

 

Sample Customers

Deutsche Bahn, Bon-Ton, WestJet, ARBURG, Northern Territory Government, Tata Steel Europe, Sharp Corporation
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 MQ vs. Redis and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.