No more typing reviews! Try our Samantha, our new voice AI agent.

Apache Pulsar vs Confluent 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

Apache Pulsar
Ranking in Streaming Analytics
22nd
Average Rating
8.0
Reviews Sentiment
6.2
Number of Reviews
1
Ranking in other categories
No ranking in other categories
Confluent
Ranking in Streaming Analytics
7th
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 August 2026, in the Streaming Analytics category, the mindshare of Apache Pulsar is 2.9%, up from 2.2% compared to the previous year. The mindshare of Confluent is 6.4%, down from 8.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Confluent6.4%
Apache Pulsar2.9%
Other90.7%
Streaming Analytics
 

Featured Reviews

it_user1087029 - PeerSpot reviewer
Solution Architect at Vlaanderen connect.
The solution can mimic other APIs without changing a line of code
The solution operates as a classic message broker but also as a streaming platform. It operates differently than a traditional streaming platform with storage and computing handled separately. It scales easier and better than Kafka which can be stubborn. You can even make it act like Kafka because it understands Kafka APIs. There are even companies that will sell you Kafka but underneath it is Apache Pulsar. The solution is very compatible because it can mimic other APIs without changing a line of code.
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

"The solution operates as a classic message broker but also as a streaming platform."
"The most valuable is its capability to enhance the documentation process, particularly when creating software documentation."
"Our main goal is to validate whether we can build a scalable and cost-efficient way to replicate data from these various sources."
"The documentation process is fast with the tool."
"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."
"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."
"One of the best features of Confluent is that it's very easy to search and have a live status with Jira."
"The client APIs are the most valuable feature."
"Having used SharePoint in the past, when I compare with traditional, old document repositories, like SharePoint, I would definitely recommend Confluent."
 

Cons

"Documentation is poor because much of it is in Chinese with no English translation."
"Confluent has a good monitoring tool, but it's not customizable."
"There is a limitation when it comes to seamlessly importing Microsoft documents into Confluent pages, which can be inconvenient for users who frequently work with Microsoft Office tools and need to transition their content to Confluent."
"The Schema Registry service could be improved. I would like a bigger knowledge base of other use cases and more technical forums. It would be good to have more flexible monitoring features added to the next release as well."
"Confluent's price needs improvement."
"The pricing was high for our needs. We should not have to pay for features we do not use."
"It would be great if the knowledge based documents in the support portal could be available for public use as well."
"It could be more user-friendly and centralized. A way to reduce redundancy would be helpful."
"One area we've identified that could be improved is the governance and access control to the Kafka topics. We've found some limitations, like a threshold of 10,000 rules per cluster, that make it challenging to manage access at scale if we have many different data sources."
 

Pricing and Cost Advice

Information not available
"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."
"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"It comes with a high cost."
"Confluent is highly priced."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"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."
"The solution is cheaper than other products."
"You have to pay additional for one or two features."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Outsourcing Company
8%
Government
7%
Comms Service Provider
7%
Financial Services Firm
15%
Retailer
12%
Computer Software Company
8%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise17
 

Questions from the Community

Ask a question
Earn 20 points
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 ...
What is your primary use case for Confluent?
The main use cases for Confluent are log aggregation and streaming. I'm familiar with Confluent stream processing with KSQL. KSQL helps in terms of data analytics strategies because if we are the d...
 

Comparisons

 

Overview

 

Sample Customers

Information Not Available
ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Find out what your peers are saying about Databricks, Microsoft, Apache and others in Streaming Analytics. Updated: July 2026.
908,800 professionals have used our research since 2012.