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

ActiveMQ vs Amazon SQS 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

ActiveMQ
Ranking in Message Queue (MQ) Software
2nd
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
28
Ranking in other categories
No ranking in other categories
Amazon SQS
Ranking in Message Queue (MQ) Software
3rd
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
31
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the Message Queue (MQ) Software category, the mindshare of ActiveMQ is 22.4%, down from 25.7% compared to the previous year. The mindshare of Amazon SQS is 7.6%, down from 9.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Queue (MQ) Software Market Share Distribution
ProductMarket Share (%)
ActiveMQ22.4%
Amazon SQS7.6%
Other70.0%
Message Queue (MQ) Software
 

Featured Reviews

MD
Software Engineer III at a financial services firm with 10,001+ employees
Integration capabilities enhance message handling without human interaction
With ActiveMQ there should be more options. If you work with other technologies, for example, Java, there are many options. We can integrate the way we want ActiveMQ. We can create partitions and clusters, but AP is not providing such options currently. It only provides time, request response timing, the number of requests that need to be handled, and protocol types. The configuration needs to be broadened inside AP to perform in a better way. Sometimes issues arise in production with ActiveMQ due to the number of requests. For example, if you have configured one thousand requests at a time and it receives one thousand and one messages at a time, it breaks. The configuration aspect is tricky. When configurations are proper, ActiveMQ almost has zero errors.
reviewer2281650 - PeerSpot reviewer
IT Specialist at a financial services firm with 51-200 employees
Efficient data retention and high scalability drive significant productivity improvements
The features of Amazon SQS that I find most valuable include its data retention capabilities and message durability. The retention of data is crucial, as other systems like RabbitMQ or ActiveMQ require management. Furthermore, if there's a failure in the system after consuming a message, SQS's settings ensure the message is not deleted until confirmation. Additionally, generating FIFO and standard queues based on use cases is a helpful feature.

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 this solution is the holding and forwarding."
"ActiveMQ brings the most value to small applications because it will not cost you very much to complete."
"I am impressed with the tool’s latency. Also, the messages in ActiveMQ wait in a queue. The messages will start to move when the system reopens after getting stuck."
"It’s a JMS broker, so the fact that it can allow for asynchronous communication is valuable."
"Message broadcasting: There could be a use case sending the same message to all consumers. So as a producer, I broadcast the message to a topic. Then, whichever consumers are subscribed to the topic can consume the same message."
"We value ActiveMQ for its performance, throughput, and low latency, especially in handling large volumes of data and sequential management of topics."
"For reliable messaging, the most valuable feature of ActiveMQ for us is ensuring prompt message delivery."
"The initial setup is straightforward and only takes a few minutes."
"The most valuable features of the solution are AWS Lambda services, ECS, and QuickSight reports, which are beneficial for data analysis."
"It is stable and scalable."
"The most valuable feature of Amazon SQS is the interface."
"There is no setup just some easy configuration required."
"The solution is easy to scale and cost-effective."
"I think the tool is very reliable."
"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."
 

Cons

"For additional functionality, I suggest making it easier to install and monitor the queues, topics, broker status, publisher status, and consumer status. Improved monitoring tools would help avoid needing to manually access the server for monitoring purposes."
"The clustering for sure needs improvement. When we were using it, the only thing available was an active/passive relationship that had to be maintained via shared file storage. That model includes a single point of failure in that storage medium."
"Distributed message processing would be a nice addition."
"It does not scale out well. It ends up being very complex if you have a lot of mirror queues."
"The solution can improve the other protocols to equal the AMQ protocol they offer."
"Message Management: Better management of the messages. Perhaps persist them, or put in another queue with another life cycle."
"Sometimes issues arise in production with ActiveMQ due to the number of requests. For example, if you have configured one thousand requests at a time and it receives one thousand and one messages at a time, it breaks."
"From the TPS point of view, it's like 100,000 transactions that need to be admitted from different devices and also from the different minor small systems. Those are best fit for Kafka. We have used it on the customer side, and we thought of giving a try to ActiveMQ, but we have to do a lot of performance tests and approval is required before we can use it for this scale."
"Be cautious around pay-as-you-use licensing as costs can become expensive."
"There is room for improvement by making use of Kafka services to create more flexible data streams."
"Sending or receiving messages takes some time, and it could be quicker."
"It would be easier to have a dashboard that allows us to see everything and manage everything since we have so many queues."
"Packages sometimes have delays in dropping, indicating reliability issues."
"The retention period for messages could be improved. Currently, messages are retained for four or seven days."
"Improvement is needed in terms of troubleshooting and logs."
"There is room for improvement in the pricing, especially for the FIFO model."
 

Pricing and Cost Advice

"I use open source with standard Apache licensing."
"There are no fees because it is open-source."
"ActiveMQ is open source, so it is free to use."
"We are using the open-source version, so we have not looked at any pricing."
"It’s open source, ergo free."
"We use the open-source version."
"The solution is less expensive than its competitors."
"I think the software is free."
"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."
"Amazon SQS is quite expensive and is at the highest price point compared to other solutions."
"Compared to the other options and based on what I have heard, Amazon SQS is relatively more expensive, but it is not insanely expensive."
"SQS's pricing is very good - I would rate it nine out of ten."
"The pricing model is pay-as-you-use. It depends on your usage and configuration."
"Amazon SQS is moderately priced."
"The pricing of Amazon SQS is reasonable. The first million requests are free every month, and after, it's cost 40 cents for every million requests. There are not any additional fees."
"Amazon SQS is more affordable compared to other solutions."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
881,733 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
30%
Computer Software Company
10%
Manufacturing Company
8%
Government
7%
Computer Software Company
20%
Financial Services Firm
13%
Comms Service Provider
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise4
Large Enterprise17
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise4
Large Enterprise14
 

Questions from the Community

What do you like most about ActiveMQ?
For reliable messaging, the most valuable feature of ActiveMQ for us is ensuring prompt message delivery.
What needs improvement with ActiveMQ?
Pricing is something to consider with ActiveMQ, though cloud pricing is not costly and depends upon the compute selection. Focusing on AI is essential nowadays. AI capabilities require improvement ...
What is your primary use case for ActiveMQ?
In my current organization, I'm only working with ActiveMQ. I previously worked with IBM WebSphere MQ.
What needs improvement with Amazon SQS?
There is nothing I can remember that I would want as new features for Amazon SQS.
What is your primary use case for Amazon SQS?
If you need a messaging service to help decouple your application, Amazon SQS would be a smart choice because it's easy to use and very easy to manage.
 

Comparisons

 

Also Known As

AMQ
No data available
 

Overview

 

Sample Customers

University of Washington, Daugherty Systems, CSC, STG Technologies, Inc. 
EMS, NASA, BMW, Capital One
Find out what your peers are saying about ActiveMQ vs. Amazon SQS and other solutions. Updated: February 2026.
881,733 professionals have used our research since 2012.