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

Featured Reviews

Sther Martins - PeerSpot reviewer
An easy-to-learn solution that can be used with microservices
We have done around 20 projects in Red Hat AMQ. I have two projects using Red Hat AMQ, and I can share how its scalability has impacted them. In one project, we have a solution for authentication and authorization using SSO. We need to integrate with other systems in two ways. We use Red Hat AMQ for social data, sending messages to other queues, and integrating with business. We have two databases with the same information. The solution is good because it helps us solve problems with messaging. For instance, when messaging doesn't change, we still check the cloud and verify the information. In another project, we have a large banking solution for the Amazon region using Red Hat AMQ for financial transactions. In this solution, business messages are sent, and another system processes them.
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 very lightweight, easy to configure, simple to manage, and robust since it launched."
"My impression is that it is average in terms of scalability."
"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."
"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."
"Reliability is the main criterion for selecting this tool for one of the busiest airports in Mumbai."
"I can organize the tool with microservices, which allows me to use it across different services. It is easy to learn."
"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."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"Redis has multiple valuable features such as being a free and reliable open-source tool."
"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."
"The solution is fast, provides good performance, and is not too expensive."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"Redis is a simple service that does what it promises."
"Redis is good for distributed caching management."
"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."
 

Cons

"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."
"AMQ could be better integrated with Jira and patch management tools."
"The challenge is the multiple components it has. This brings a higher complexity compared to IBM MQ, which is a single complete unit."
"The product needs to improve its documentation and training."
"There are some aspects of the monitoring that could be improved on. There is a tool that is somewhat connected to Kafka called Service Registry. This is a product by Red Hat that I would like to see integrated more tightly."
"There is improvement needed to keep the support libraries updated."
"This product needs better visualization capabilities in general."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"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."
"Redis presents a single point of failure and lacks fault tolerance."
"There is a lack of documentation on the scalability of the solution."
"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."
"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 initial setup of Redis was difficult, with a rating of two or three out of ten."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
 

Pricing and Cost Advice

"There is a subscription needed for this solution and there are support plans available."
"The solution is open-source."
"Red Hat AMQ's pricing could be improved."
"This is a very cost-effective solution and the pricing is much better than competitors."
"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."
"The tool is open-source. There are no additional costs."
"Redis is not an overpriced solution."
"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.
865,384 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
24%
Computer Software Company
13%
Government
10%
Manufacturing Company
6%
Financial Services Firm
24%
Computer Software Company
13%
Educational Organization
7%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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: July 2025.
865,384 professionals have used our research since 2012.