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

Red Hat AMQ vs Redis comparison

Why PeerSpot?
 

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

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.
RituRaj - PeerSpot reviewer
SDE 2 at Virtusa
Caching has improved response times and reduces database load for high-traffic applications
Redis is very reliable, but it could be improved in areas such as monitoring, debugging, and feasibility into memory use. Better built-in tools for observability would help teams manage it more effectively at scale. Managing memory efficiently and troubleshooting issues can sometimes require additional tooling, so these areas can also be improved.One practical challenge I experienced is managing memory efficiently. Since Redis is in-memory, we need to carefully configure eviction policies and monitor usage. Debugging cache-related issues such as stale data or cache invalidation can sometimes be tricky. Additionally, tuning memory usage and eviction policies needs to be planned very carefully.

Quotes from Members

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

Pros

"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."
"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."
"My impression is that it is average in terms of scalability."
"The solution is very lightweight, easy to configure, simple to manage, and robust since it launched."
"The most valuable feature is stability."
"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 self-service aspect is very important for us, and AMQ Streams has enabled us to deliver new services faster, going from days to hours."
"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, and it also shows utilization in the tool."
"Redis is a simple service that does what it promises."
"The performance of Redis is very fast."
"Redis is a powerful and reliable tool for improving application performance."
"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."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"Since I started using Redis, I feel that the product is saving me some performance tuning time."
"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."
"Redis is a simple, powerful, and fast solution."
 

Cons

"The turnaround of adopting new versions of underlying technologies sometimes is too slow."
"This solution is completely unstable. We lose messages."
"Red Hat AMQ's cost could be improved, and it could have better integration."
"The product needs to improve its documentation and training."
"There are some aspects of the monitoring that could be improved on."
"The areas for improvement include cost, which is a primary concern."
"AMQ could be better integrated with Jira and patch management tools."
"There is improvement needed to keep the support libraries updated."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"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."
"For the PubSub feature, we had to create our own tools to monitor the events."
"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 first challenge is memory limitations, as Redis is primarily in-memory, making memory usage a key constraint."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"The only thing is the lack of a GUI application. There was a time when we needed to resolve an issue in production. If we had a GUI, it would have been easier."
"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."
"The solution is open-source."
"Red Hat AMQ's pricing could be improved."
"I would rate the pricing a six out of ten, with ten being expensive."
"The tool is open-source. There are no additional costs."
"Redis is not an overpriced solution."
"Redis is an open-source solution. There are not any hidden fees."
"Redis is an open-source product."
"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.
913,683 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
9%
Outsourcing Company
9%
Government
8%
Financial Services Firm
22%
Computer Software Company
9%
Comms Service Provider
7%
University
5%
 

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 Business13
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 needs improvement with Redis?
Making management easier, especially for teams operating large Redis clusters, would be helpful. More advanced built-in observability, performance insights, and automated recommendations would help...
What is your primary use case for Redis?
Redis is used primarily as a caching layer to provide a high-performance caching solution that improves application response times and reduces load on backend services and databases. We use it main...
What advice do you have for others considering Redis?
There are a couple of things to consider when using Redis. It is a supporting layer, not a main database. Identifying specific use cases where Redis can provide the most value, such as caching, ses...
 

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 IBM, Apache, Amazon Web Services (AWS) and others in Message Queue (MQ) Software. Updated: September 2026.
913,683 professionals have used our research since 2012.