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

Apache Kafka vs Confluent comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

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

Apache Kafka
Ranking in Streaming Analytics
7th
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
90
Ranking in other categories
No ranking in other categories
Confluent
Ranking in Streaming Analytics
5th
Average Rating
8.2
Reviews Sentiment
6.3
Number of Reviews
25
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2026, in the Streaming Analytics category, the mindshare of Apache Kafka is 4.2%, up from 2.4% compared to the previous year. The mindshare of Confluent is 6.9%, down from 8.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Confluent6.9%
Apache Kafka4.2%
Other88.9%
Streaming Analytics
 

Featured Reviews

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.
PavanManepalli - PeerSpot reviewer
AVP - Sr Middleware Messaging Integration Engineer at Wells Fargo
Has supported streaming use cases across data centers and simplifies fraud analytics with SQL-based processing
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools. They need to improve in that direction by not only reducing costs but also providing better solutions for the problems customers face to avoid frustrations, whether through future enhancement requests or ensuring product stability. The cost should be worked on, and they should provide better solutions for customers. Solutions should focus on hierarchical topics; if a customer has different types of data and sources, they should be able to send them to the same place for analytics. Currently, Confluent requires everything to send to the same topic, which becomes very large and makes running analytics difficult. The hierarchy of topics should be improved. This part is available in MQ and other products such as Solace, but it is missing in Confluent, leading many in capital markets and trading to switch to Solace. In terms of stability, it is not the stability itself that needs improvement but rather the delivery semantics. Other products offer exactly-once delivery out of the box, whereas Confluent states it will offer this but lacks the knobs or levers for tuning configurations effectively. Confluent has hundreds of configurations that application teams must understand, which creates a gap. Users are often unaware of what values to set for better performance or to achieve exactly-once semantics, making it difficult to navigate through them. Delivery semantics also need to be worked on.

Quotes from Members

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

Pros

"Excellent speeds for publishing messages faster."
"A great streaming platform."
"Apache Kafka is an open-source solution that can be used for messaging or event processing."
"The stream processing is a very valuable aspect of the solution for us."
"It has become dead simple to connect different application and services, saving a lot of development hours."
"Kafka is a highly scalable product."
"Excellent speeds for publishing messages faster."
"Apache Kafka's most valuable features include clustering and sharding...It is a pretty stable solution."
"With Confluent Cloud we no longer need to handle the infrastructure and the plumbing, which is a concern for Confluent. The other advantage is that all portfolios have access to the data that is being shared."
"The most valuable is its capability to enhance the documentation process, particularly when creating software documentation."
"Implementing Confluent's schema registry has significantly enhanced our organization's data quality assurance."
"I would rate the scalability of the solution at eight out of ten. We have 20 people who use Confluent in our organization now, and we hope to increase usage in the future."
"The design of the product is extremely well built and it is highly configurable."
"The benefit is escaping email communication. Sometimes people ignore emails or put them into spam, but with Confluence, everyone sees the same text at the same time."
"Confluence's greatest asset is its user-friendly interface, coupled with its remarkable ability to seamlessly integrate with a vast range of other solutions."
"I find Confluent's Kafka Connectors and Kafka Streams invaluable for my use cases because they simplify real-time data processing and ETL tasks by providing reliable, pre-packaged connectors and tools."
 

Cons

"The repository isn't working very well. It's not user friendly."
"The solution's initial setup process was complex."
"There are some latency problems with Kafka."
"We used to have problems in Kafka every three weeks and our dev ops team fixed a few issues."
"An area for improvement would be growth."
"I suggest using cloud services because the solution is expensive if you are using it on-premises."
"We struggled a bit with the built-in data transformations because it was a challenge to get them up and running the way we wanted."
"While the solution scales well and easily, you need to understand your future needs and prep for the peaks."
"They should remove Zookeeper because of security issues."
"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"Confluent's price needs improvement."
"It could be more user-friendly and centralized. A way to reduce redundancy would be helpful."
"It would help if the knowledge based documents in the support portal could be available for public use as well."
"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
"The formatting aspect within the page can be improved and more powerful."
"Currently, in the early stages, I see a gap on the security side. If you are using the SaaS version, we would like to get a fuller, more secure solution that can be adopted right out of the box. Confluence could do a better job sharing best practices or a reusable pattern that others have used, especially for companies that can not afford to hire professional services from Confluent."
 

Pricing and Cost Advice

"This is an open-source solution and is free to use."
"It is approximately $600,000 USD."
"The cost can vary depending on the provider and the specific flavor or version you use. I'm not very knowledgeable about the pricing details."
"When starting to look at a distributed message system, look for a cloud solution first. It is an easier entry point than an on-premises hardware solution."
"The price of Apache Kafka is good."
"The solution is open source; it's 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."
"I would not subscribe to the Confluent platform, but rather stay on the free open source version. The extra cost wasn't justified."
"You have to pay additional for one or two features."
"Confluent is an expensive solution."
"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"On a scale from one to ten, where one is low pricing and ten is high pricing, I would rate Confluent's pricing at five. I have not encountered any additional costs."
"The pricing model of Confluent could improve because if you have a classic use case where you're going to use all the features there is no plan to reduce the features. You should be able to pick and choose basic services at a reduced price. The pricing was high for our needs. We should not have to pay for features we do not use."
"Regarding pricing, I think Confluent is a premium product, but it's hard for me to say definitively if it's overly expensive. We're still trying to understand if the features and reduced maintenance complexity justify the cost, especially as we scale our platform use."
"It comes with a high cost."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
884,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
10%
Manufacturing Company
10%
Comms Service Provider
5%
Financial Services Firm
15%
Computer Software Company
11%
Retailer
11%
Manufacturing Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business32
Midsize Enterprise18
Large Enterprise49
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise16
 

Questions from the Community

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.
What do you like most about Confluent?
I find Confluent's Kafka Connectors and Kafka Streams invaluable for my use cases because they simplify real-time data processing and ETL tasks by providing reliable, pre-packaged connectors and to...
What is your experience regarding pricing and costs for Confluent?
They charge a lot for scaling, which makes it expensive.
What needs improvement with Confluent?
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about ...
 

Comparisons

 

Overview

 

Sample Customers

Uber, Netflix, Activision, Spotify, Slack, Pinterest
ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Find out what your peers are saying about Apache Kafka vs. Confluent and other solutions. Updated: March 2026.
884,873 professionals have used our research since 2012.