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

Red Hat AMQ 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

Red Hat AMQ
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
10
Ranking in other categories
Message Queue (MQ) Software (7th)
Redis
Average Rating
8.8
Reviews Sentiment
5.9
Number of Reviews
26
Ranking in other categories
NoSQL Databases (4th), Managed NoSQL Databases (6th), In-Memory Data Store Services (1st), Vector Databases (4th), AI Software Development (13th)
 

Featured Reviews

SachinJain - PeerSpot reviewer
Senior Technical Specialist at Intuitive Technology Partners
Efficiently manages high availability and fault tolerance for critical systems with user-friendly management features
I have experience with features such as message persistence and fault tolerance because I configured high availability and fault tolerance for the client environment, including active-active and active-passive configurations. I mainly prefer active-active. I created a security feature for user authentication and authorization in Red Hat AMQ using vault. When you enable the vault, then your whole Red Hat AMQ becomes more secure. Management is straightforward. I configured it and created documentation. The operations team takes care of the operation part. I educate them on how to manage access, so they can easily add new people who join the company or manage the people who leave. The benefits of using Red Hat AMQ include easy configuration and monitoring. On the portal, I can monitor how many packets or alerts have been generated or sent to the end user via Red Hat AMQ along with messages or emails. It also shows utilization in the tool. These features also come with other AMQs such as Amazon and IBM.
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

"This product is well adopted on the OpenShift platform. For organizations like ours that use OpenShift for many of our products, this is a good feature."
"The solution is very lightweight, easy to configure, simple to manage, and robust since it launched."
"The most valuable feature for us is the operator-based automation that is provided by Streams for infrastructure as well as user and topic management. This saves a lot of time and effort on our part to provide infrastructure. For example, the deployment of infrastructure is reduced from approximately a week to a day."
"From the functionality perspective, 3scale provides a very comparable, if not the same feature set as any leader in the market for API management and the gateway perspective, but with a fraction of the price."
"AMQ is highly scalable and performs well. It can process a large volume of messages in one second. AMQ and OpenShift are a good combination."
"The self-service aspect is very important for us, and AMQ Streams has enabled us to deliver new services faster, going from days to hours."
"My impression is that it is average in terms of scalability."
"Reliability is the main criterion for selecting this tool for one of the busiest airports in Mumbai."
"Redis is a simple service that does what it promises."
"I use Redis mostly to cache repeated data that is required."
"Redis acts as an in-memory search tool that improves the speed of operations."
"Redis has multiple valuable features such as being a free and reliable open-source tool."
"The performance of Redis is very fast."
"Redis is a powerful and reliable tool for improving application performance."
"The ability to fetch and save data quickly is valuable."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
 

Cons

"The turnaround of adopting new versions of underlying technologies sometimes is too slow."
"Red Hat AMQ's cost could be improved, and it could have better integration."
"The turnaround of adopting new versions of underlying technologies sometimes is too slow."
"There is improvement needed to keep the support libraries updated."
"This solution is completely unstable. We lose messages."
"This product needs better visualization capabilities in general."
"There are some aspects of the monitoring that could be improved on."
"The challenge is the multiple components it has. This brings a higher complexity compared to IBM MQ, which is a single complete unit."
"There is a lack of documentation on the scalability of the solution."
"For the PubSub feature, we had to create our own tools to monitor the events."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"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."
"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."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
"There are some points where I feel Redis can be improved."
"The solution's pricing for a local installation is very expensive."
 

Pricing and Cost Advice

"There is a subscription needed for this solution and there are support plans available."
"This is a very cost-effective solution and the pricing is much better than competitors."
"Red Hat AMQ's pricing could be improved."
"The solution is open-source."
"I would rate the pricing a six out of ten, with ten being expensive."
"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."
"Redis is not an overpriced solution."
"We saw an ROI. It made the processing of our transactions faster."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Manufacturing Company
9%
Government
8%
Computer Software Company
7%
Financial Services Firm
24%
Computer Software Company
10%
Comms Service Provider
7%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise4
Large Enterprise2
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise6
Large Enterprise10
 

Questions from the Community

What needs improvement with Red Hat AMQ?
The areas for improvement include cost, which is a primary concern. The deployment process is simple, but the cost is very important. Additionally, the management portal should be more user-friendl...
What is your primary use case for Red Hat AMQ?
For use cases for Red Hat AMQ, let's take banking purposes. This depends upon the firm or the service or product company. For example, let's take HDFC Bank or any other bank. Whenever a customer de...
What advice do you have for others considering Red Hat AMQ?
I work primarily with Red Hat. For IBM, I have worked with their channel partner, not directly with IBM. For Amazon, I work with partners only. I am working with one company as a consultant. I also...
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

Red Hat JBoss A-MQ, Red Hat JBoss AMQ
Redis Enterprise
 

Overview

 

Sample Customers

E*TRADE, CERN, CenturyLink, AECOM, Sabre Holdings
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 Red Hat AMQ vs. Redis and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.