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
7.8
Reviews Sentiment
7.1
Number of Reviews
26
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.4
Number of Reviews
30
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the Message Queue (MQ) Software category, the mindshare of ActiveMQ is 26.4%, up from 21.8% compared to the previous year. The mindshare of Amazon SQS is 8.3%, down from 11.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Queue (MQ) Software
 

Featured Reviews

Prashant-Sharma - PeerSpot reviewer
Allows for asynchronous communication, enabling services to operate independently but issues with stability
The feature of ActiveMQ which I feel is good is its ability to have DLP, the later queues. If something goes wrong with the platform, it retries. Even if it fails, it goes to DLP, and later we can rescan the same event for processing. The ability to store the failed events for some time is valuable.
Ariel Tarayants - PeerSpot reviewer
Powerful queue system facilitates seamless asynchronous operations
A feature I would like to see in Amazon SQS is the ability to view the content of messages without removing them from the queue. Enhanced filtering on the messages would be beneficial, as currently one has to pull all messages out, filter the right one by code, and then re-insert the remaining messages. This solution is not effective with the FIFO queue.

Quotes from Members

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

Pros

"The ability to store the failed events for some time is valuable."
"It’s a JMS broker, so the fact that it can allow for asynchronous communication is valuable."
"Most people or many people recommended using ActiveMQ on small and medium-scale applications."
"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 provides the best support services."
"The initial setup is straightforward and only takes a few minutes."
"I'm impressed, I think that Active MQ is great."
"For reliable messaging, the most valuable feature of ActiveMQ for us is ensuring prompt message delivery."
"The most valuable feature of Amazon SQS is its scalability."
"The most valuable feature of Amazon SQS is the interface."
"SQS is very stable, and it has lots of features."
"With SQS, we can trigger events in various cloud environments. It offers numerous benefits for us."
"It's very quick and easy to build or set up Amazon SQS."
"We use SNS as the publisher, and our procurement service subscribes to those events using SQS. In the past, we relied on time-based or batch-based processes to send data between services on-premises. With SQS, we can trigger actions based on real-time changes in business processes, improving reliability."
"The scale it manages is quite impressive."
"The solution is easy to scale and cost-effective."
 

Cons

"Needs to focus on a certain facet and be good at it, instead of handling support for most of the available message brokers."
"It would be great if it is included as part of the solution, as Kafka is doing. Even though the use case of Kafka is different, If something like data extraction is possible, or if we can experiment with partition tolerance and other such things, that will be great."
"One potential area would be the complexity of the initial setup."
"I would like the tool to improve compliance and stability. We will encounter issues while using the central applications. In the solution's future releases, I want to control and set limitations for databases."
"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."
"The solution's stability needs improvement."
"This solution could improve by providing better documentation."
"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."
"It would be easier to have a dashboard that allows us to see everything and manage everything since we have so many queues."
"The current visibility timeout of five minutes is okay. However, I'd like to explore the possibility of extending it for specific use cases."
"Amazon SQS is costly. I think there could be improvements in how it facilitates comparisons between different AWS products. A calculator would be helpful. The calculator for Kafka is based on factors like throughput or storage used in the last month. In contrast, the calculator for Amazon SQS is based on the number of transactions processed. These different approaches make it challenging to compare them directly. I suggest AWS provide a straightforward calculator where I can input one aspect, and it calculates costs for multiple solutions."
"The initial setup of Amazon SQS is in the middle range of difficulty. You need to learn Amazon AWS and know how to navigate, create resources, and structures, and provide rules."
"A feature I would like to see in Amazon SQS is the ability to view the content of messages without removing them from the queue."
"The solution is not available on-premises so that rules out any customers looking for the messaging solution on-premises."
"I do not think that this solution is easy to use and the documentation of this solution has a lot of problems and can be improved in the next release. Most of the time, the images in the document are from older versions."
"The cost became an issue, leading us to consider other solutions."
 

Pricing and Cost Advice

"ActiveMQ is open source, so it is free to use."
"The solution is less expensive than its competitors."
"We use the open-source version."
"We are using the open-source version, so we have not looked at any pricing."
"I use open source with standard Apache licensing."
"I think the software is free."
"The tool's pricing is reasonable and competitive compared to other solutions."
"It’s open source, ergo free."
"It's quite expensive."
"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."
"Compared to EC2 and other services, Amazon SQS' pricing is cheaper."
"The pricing model is pay-as-you-use. It depends on your usage and configuration."
"Amazon SQS is moderately priced."
"SQS's pricing is very good - I would rate it nine out of ten."
"Amazon SQS is more affordable 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."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
849,686 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
34%
Computer Software Company
11%
Manufacturing Company
9%
Government
7%
Computer Software Company
19%
Financial Services Firm
16%
Manufacturing Company
11%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
We need to address the non-deterministic load issues. Sometimes, ActiveMQ either restarts automatically or goes into ActiveMQ mode, causing interruptions. We need to enhance stability and improve t...
What is your primary use case for ActiveMQ?
We have a digital ID platform that uses various services running on Kafka. There are two main endpoints where services interact with external services. These include an automatic biometric service ...
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...
 

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: April 2025.
849,686 professionals have used our research since 2012.