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

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 (6th)
Redis
Average Rating
8.8
Reviews Sentiment
5.7
Number of Reviews
23
Ranking in other categories
NoSQL Databases (7th), Managed NoSQL Databases (9th), In-Memory Data Store Services (1st), Vector Databases (4th)
 

Featured Reviews

SachinJain - PeerSpot reviewer
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.
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 most valuable feature is stability."
"Red Hat AMQ's best feature is its reliability."
"The solution is very lightweight, easy to configure, simple to manage, and robust since it launched."
"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."
"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."
"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."
"My impression is that it is average in terms of scalability."
"I can organize the tool with microservices, which allows me to use it across different services. It is easy to learn."
"The online interface is very fast and easy to use."
"Redis acts as an in-memory search tool that improves the speed of operations."
"Redis is good for distributed caching management."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"It is particularly efficient for cloud-based storage and operations."
"I use Redis mostly to cache repeated data that is required."
"The product offers fast access to my database."
"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."
 

Cons

"There are several areas in this solution that need improvement, including clustering multi-nodes and message ordering."
"There is improvement needed to keep the support libraries updated."
"The product needs to improve its documentation and training."
"This product needs better visualization capabilities in general."
"AMQ could be better integrated with Jira and patch management tools."
"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."
"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 room for AWS to provide more options for server types or a way to configure more or less memory for them."
"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."
"The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly."
"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 presents a single point of failure and lacks fault tolerance."
"If we use a lot of data, it will eventually cost us a lot."
"The solution's pricing for a local installation is very expensive."
"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."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
Financial Services Firm
25%
Computer Software Company
13%
Government
9%
Manufacturing Company
7%
Financial Services Firm
25%
Computer Software Company
12%
Educational Organization
7%
Comms Service Provider
7%
 

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 Enterprise3
Large Enterprise8
 

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

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: September 2025.
869,566 professionals have used our research since 2012.