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

ActiveMQ vs Apache Kafka 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

ActiveMQ
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
28
Ranking in other categories
Message Queue (MQ) Software (2nd)
Apache Kafka
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
90
Ranking in other categories
Streaming Analytics (7th)
 

Mindshare comparison

ActiveMQ and Apache Kafka aren’t in the same category and serve different purposes. ActiveMQ is designed for Message Queue (MQ) Software and holds a mindshare of 22.4%, down 25.7% compared to last year.
Apache Kafka, on the other hand, focuses on Streaming Analytics, holds 4.0% mindshare, up 2.3% since last year.
Message Queue (MQ) Software Market Share Distribution
ProductMarket Share (%)
ActiveMQ22.4%
IBM MQ22.9%
Red Hat AMQ8.9%
Other45.800000000000004%
Message Queue (MQ) Software
Streaming Analytics Market Share Distribution
ProductMarket Share (%)
Apache Kafka4.0%
Apache Flink11.3%
Databricks9.5%
Other75.2%
Streaming Analytics
 

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.
Bruno da Silva - PeerSpot reviewer
Senior Manager at Timestamp, SA
Have worked closely with the team to deploy streaming and transaction pipelines in a flexible cloud environment
The interface of Apache Kafka could be significantly better. I started working with Apache Kafka from its early days, and I have seen many improvements. The back office functionality could be enhanced. Scaling up continues to be a challenge, though it is much easier now than it was in the beginning.

Quotes from Members

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

Pros

"ActiveMQ demonstrates excellent stability and sturdiness."
"The most valuable feature of this solution is the holding and forwarding."
"ActiveMQ is very lightweight and quick."
"For reliable messaging, the most valuable feature of ActiveMQ for us is ensuring prompt message delivery."
"It’s a JMS broker, so the fact that it can allow for asynchronous communication is valuable."
"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."
"Most people or many people recommended using ActiveMQ on small and medium-scale applications."
"The most important feature is that it's best for JVM-related languages and JMS integration."
"It is a useful way to maintain messages and to manage offset from our consumers."
"A great streaming platform."
"Deployment is speedy."
"When comparing it with other messaging and integration platforms, this is one of the best rated."
"The most important feature for me is the guaranteed delivery of messages from producers to consumers."
"The solution is very easy to set up."
"With Kafka, events and streaming are persistent, and multiple subscribers can consume the data. This is an advantage of Kafka compared to simple queue-based solutions."
"Apache Kafka is a mature product and can handle a massive amount of data in real time for data consumption."
 

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."
"AI capabilities require improvement in future updates."
"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."
"I would rate the stability a five out of ten because sometimes it gets stuck, and we have to restart it. We"
"Message Management: Better management of the messages. Perhaps persist them, or put in another queue with another life cycle."
"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 solution can improve the other protocols to equal the AMQ protocol they offer."
"would like to see real-time event-based consumption of messages rather than the traditional way through a loop. The traditional messaging system works by listing and looping with a small wait to check to see what the messages are. A push system is where you have something that is ready to receive a message and when the message comes in and hits the partition, it goes straight to the consumer versus the consumer having to pull. I believe this consumer approach is something they are working on and may come in an upcoming release. However, that is message consumption versus message listening."
"The third party is not very stable and sometimes you have problems with this component. There are some developments in newer versions and we're about to try them out, but I'm not sure if it closes the gap."
"Too much dependency on the zookeeper and leader selection is still the bottleneck for Kafka implementation."
"Kafka has a lot of monitors, but sometimes it's most important to just have a simple monitor."
"One complexity that I faced with the tool stems from the fact that since it is not kind of a stand-alone application, it won't integrate with native cloud, like AWS or Azure."
"They need to have a proper portal to do everything because, at this moment, Kafka is lagging in this regard."
"It’s a trial-and-error process with no one-size-fits-all solution. Issues may arise until it’s appropriately tuned."
"The interface has room for improvement, and there is a steep learning curve for Hadoop integration. It was a struggle learning to send from Hadoop to Kafka. In future releases, I'd like to see improvements in ETL functionality and Hadoop integration."
 

Pricing and Cost Advice

"The solution is less expensive than its competitors."
"The tool's pricing is reasonable and competitive compared to other solutions."
"There are no fees because it is open-source."
"I think the software is free."
"We use the open-source version."
"We are using the open-source version, so we have not looked at any pricing."
"It’s open source, ergo free."
"ActiveMQ is open source, so it is free to use."
"I rate Apache Kafka's pricing a five on a scale of one to ten, where one is cheap and ten is expensive. There are no additional costs apart from the licensing fees for Apache Kafka."
"We are using the free version of Apache Kafka."
"Licensing issues are not applicable. Apache licensing makes it simple with almost zero cost for the software itself."
"It is approximately $600,000 USD."
"This is an open-source solution and is free to use."
"It's a bit cheaper compared to other Q applications."
"I was using the product's free version."
"It is open source software."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
881,707 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%
Financial Services Firm
20%
Computer Software Company
11%
Manufacturing Company
9%
Retailer
5%
 

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 Business32
Midsize Enterprise18
Large Enterprise49
 

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 are the differences between Apache Kafka and IBM MQ?
Apache Kafka is open source and can be used for free. It has very good log management and has a way to store the data used for analytics. Apache Kafka is very good if you have a high number of user...
What is your experience regarding pricing and costs for Apache Kafka?
Its pricing is reasonable. It's not always about cost, but about meeting specific needs.
What needs improvement with Apache Kafka?
The long-term data storage feature in Apache Kafka depends on the setting, but I believe the maximum duration is seven days.
 

Comparisons

 

Also Known As

AMQ
No data available
 

Overview

 

Sample Customers

University of Washington, Daugherty Systems, CSC, STG Technologies, Inc. 
Uber, Netflix, Activision, Spotify, Slack, Pinterest
Find out what your peers are saying about ActiveMQ vs. Apache Kafka and other solutions. Updated: May 2024.
881,707 professionals have used our research since 2012.