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
29
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Message Queue (MQ) Software category, the mindshare of ActiveMQ is 26.5%, up from 21.3% compared to the previous year. The mindshare of Amazon SQS is 8.5%, down from 11.6% 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 most valuable feature of this solution is the holding and forwarding."
"For reliable messaging, the most valuable feature of ActiveMQ for us is ensuring prompt message delivery."
"Most people or many people recommended using ActiveMQ on small and medium-scale applications."
"The ability to store the failed events for some time is valuable."
"The initial setup is straightforward and only takes a few minutes."
"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."
"I'm impressed, I think that Active MQ is great."
"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."
"I like how we can subscribe to multiple topics in Amazon SQS. It's also much simpler and quicker to set up than other solutions. It also supports patterns like Kafka and RapidMQ's fan-out pattern but with easier implementation."
"The dead-letter queue is very helpful in maintaining the messages that come into the queue."
"One of the most valuable features of Amazon SQS is its event-driven invocation."
"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."
"The most valuable feature of Amazon SQS is the interface."
"The solution is easy to scale and cost-effective."
"We use Amazon SQS for notifying, queuing servers, queuing messages, and notifying the people for alerting systems."
 

Cons

"The tool needs to improve its installation part which is lengthy. The product is already working on that aspect so that the complete installation gets completed within a month."
"One potential area would be the complexity of the initial setup."
"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."
"Needs to focus on a certain facet and be good at it, instead of handling support for most of the available message brokers."
"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."
"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."
"We need to enhance stability and improve the deployment optimization to fully leverage the platform's capabilities."
"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."
"Sometimes, we have to switch to another component similar to SQS because the patching tool for SQS is relatively slow for us."
"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."
"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."
"It would be easier to have a dashboard that allows us to see everything and manage everything since we have so many queues."
"There could be improvements in the UI for security and scalability."
"The current visibility timeout of five minutes is okay. However, I'd like to explore the possibility of extending it for specific use cases."
"I cannot send a message to multiple people simultaneously. It can only be sent to one recipient."
 

Pricing and Cost Advice

"ActiveMQ is open source, so it is free to use."
"The tool's pricing is reasonable and competitive compared to other solutions."
"We are using the open-source version, so we have not looked at any pricing."
"It’s open source, ergo free."
"The solution is less expensive than its competitors."
"I use open source with standard Apache licensing."
"We use the open-source version."
"I think the software is free."
"Amazon SQS is quite expensive and is at the highest price point compared to other solutions."
"Amazon SQS is more affordable compared to other solutions."
"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."
"I rate the tool's pricing a nine out of ten."
"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 moderately priced."
"Compared to EC2 and other services, Amazon SQS' pricing is cheaper."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
845,406 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
6%
Computer Software Company
17%
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?
AWS provides another messaging service, which is fine for certain purposes. SQS meets the cloud messaging workload requirements. However, combining the features of both products could be an easier ...
What is your primary use case for Amazon SQS?
I primarily use SQL Server for messaging services, and I need to offer loose couplings. SQS is handy for offloading non-urgent tasks that can be reverted later. I use it as a queue management servi...
 

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: March 2025.
845,406 professionals have used our research since 2012.