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

Amazon SQS vs Red Hat AMQ comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 27, 2025

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

Amazon SQS
Ranking in Message Queue (MQ) Software
3rd
Average Rating
8.6
Reviews Sentiment
7.4
Number of Reviews
30
Ranking in other categories
No ranking in other categories
Red Hat AMQ
Ranking in Message Queue (MQ) Software
7th
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
10
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2025, in the Message Queue (MQ) Software category, the mindshare of Amazon SQS is 8.1%, down from 10.6% compared to the previous year. The mindshare of Red Hat AMQ is 9.4%, up from 8.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Queue (MQ) Software
 

Featured Reviews

Hari Prakash Pokala - PeerSpot reviewer
Valuable AWS services enhance data analysis yet could benefit from flexible data streams
I am using multiple services such as AWS Lambda, S3, EC2, ECS, and the SNS SQS services, along with QuickSight reports and some of the VPC concepts.  We have an email notification system integrated with Spring Branch. Once a batch job completes, SNS and SQS trigger events, sending notification…
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.

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 of Amazon SQS is its scalability."
"We used SQS for the Kapolei system to ensure that certain tasks were executed precisely once. The first-in, first-out (FIFO) capability was a great feature for us. Additionally, its redundancy out of the box meant we didn't have to worry about missing messages. It provided peace of mind and automatically instilled trust, relieving us of any concerns."
"I am able to find out what's going on very easily."
"The most valuable features include the ability to handle a huge number of messages and the presence of a dead letter queue."
"We use Amazon SQS for notifying, queuing servers, queuing messages, and notifying the people for alerting systems."
"One of the most valuable features of Amazon SQS is its event-driven invocation."
"The libraries that connect and manage the queues are rich in features."
"One of the useful features is the ability to schedule a call after a certain number of messages accumulate in the container. For example, if there are ten messages in the container, you can perform a specific action."
"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."
"The most valuable feature is stability."
"Reliability is the main criterion for selecting this tool for one of the busiest airports in Mumbai."
"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."
"Red Hat AMQ's best feature is its reliability."
"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."
"I can organize the tool with microservices, which allows me to use it across different services. It is easy to learn."
 

Cons

"There is room for improvement by making use of Kafka services to create more flexible data streams."
"There is room for improvement in handling large-scale data."
"There are some issues with SQS's transaction queue regarding knowing if something has been received."
"Sometimes, we have to switch to another component similar to SQS because the patching tool for SQS is relatively slow for us."
"The current visibility timeout of five minutes is okay. However, I'd like to explore the possibility of extending it for specific use cases."
"The cost became an issue, leading us to consider other solutions."
"It would be easier to have a dashboard that allows us to see everything and manage everything since we have so many queues."
"Be cautious around pay-as-you-use licensing as costs can become expensive."
"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."
"This product needs better visualization capabilities in general."
"There is improvement needed to keep the support libraries updated."
"AMQ could be better integrated with Jira and patch management tools."
"The product needs to improve its documentation and training."
"There are several areas in this solution that need improvement, including clustering multi-nodes and message ordering."
"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."
 

Pricing and Cost Advice

"It's quite expensive."
"Compared to the other options and based on what I have heard, Amazon SQS is relatively more expensive, but it is not insanely expensive."
"Amazon SQS is quite expensive and is at the highest price point compared to other solutions."
"Amazon SQS is moderately priced."
"Amazon SQS is more affordable compared to other solutions."
"Amazon SQS offers a generous free tier, beyond which it remains very cost-effective. The cost per million messages is less than a dollar, making it an economical choice."
"I rate the tool's pricing a nine out of ten."
"Compared to EC2 and other services, Amazon SQS' pricing is cheaper."
"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."
"There is a subscription needed for this solution and there are support plans available."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
865,295 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
14%
Manufacturing Company
9%
Comms Service Provider
8%
Financial Services Firm
24%
Computer Software Company
13%
Government
10%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with Amazon SQS?
The retention period for messages could be improved. Currently, messages are retained for four or seven days. It would be beneficial if there was a provision to configure and retain messages for lo...
What is your primary use case for Amazon SQS?
I primarily use Amazon SQS ( /products/amazon-sqs-reviews ) for asynchronous messaging. It is part of our distributed system design, where we use it for asynchronous communication by posting a mess...
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...
 

Comparisons

 

Also Known As

No data available
Red Hat JBoss A-MQ, Red Hat JBoss AMQ
 

Overview

 

Sample Customers

EMS, NASA, BMW, Capital One
E*TRADE, CERN, CenturyLink, AECOM, Sabre Holdings
Find out what your peers are saying about Amazon SQS vs. Red Hat AMQ and other solutions. Updated: July 2025.
865,295 professionals have used our research since 2012.