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

Confluent vs StreamSets 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

Confluent
Average Rating
8.2
Reviews Sentiment
6.3
Number of Reviews
25
Ranking in other categories
Streaming Analytics (5th)
StreamSets
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
Data Integration (21st)
 

Mindshare comparison

Confluent and StreamSets aren’t in the same category and serve different purposes. Confluent is designed for Streaming Analytics and holds a mindshare of 6.8%, down 8.5% compared to last year.
StreamSets, on the other hand, focuses on Data Integration, holds 1.2% mindshare, down 1.6% since last year.
Streaming Analytics Market Share Distribution
ProductMarket Share (%)
Confluent6.8%
Apache Flink11.3%
Databricks9.5%
Other72.4%
Streaming Analytics
Data Integration Market Share Distribution
ProductMarket Share (%)
StreamSets1.2%
SSIS3.7%
Informatica Intelligent Data Management Cloud (IDMC)3.5%
Other91.6%
Data Integration
 

Featured Reviews

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.
SS
Enterprise Solutions Architect at a energy/utilities company with 1,001-5,000 employees
Enables effective batch loading with visual interface and enterprise support
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infrastructure. I had to switch to a new EC2 box, even though the processor was not fully utilized. It would be beneficial if StreamSets addressed any potential memory leak issues to prevent unnecessary upgrades. Additionally, it would be a great enhancement if StreamSets could produce a lineage graph to visualize how the data has passed through the system.

Quotes from Members

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

Pros

"The biggest benefit of Confluent as a tool is that it is a distributed platform that provides more durability and stability."
"We mostly use the solution's message queues and event-driven architecture."
"The solution can handle a high volume of data because it works and scales well."
"Confluence's greatest asset is its user-friendly interface, coupled with its remarkable ability to seamlessly integrate with a vast range of other solutions."
"Confluent facilitates the messaging tasks with Kafka, streamlining our processes effectively."
"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."
"The monitoring module is impressive."
"The features I find most useful in Confluent are the Multi-Region Cluster, MRC, and the Cluster Linking for replication."
"What I love the most is that StreamSets is very light. It's a containerized application. It's easy to use with Docker. If you are a large organization, it's very easy to use Kubernetes."
"The most valuable feature is the pipelines because they enable us to pull in and push out data from different sources and to manipulate and clean things up within them."
"The best feature that I really like is the integration."
"Also, the intuitive canvas for designing all the streams in the pipeline, along with the simplicity of the entire product are very big pluses for me. The software is very simple and straightforward. That is something that is needed right now."
"The ability to have a good bifurcation rate and fewer mistakes is valuable."
"The best thing about StreamSets is its plugins, which are very useful and work well with almost every data source. It's also easy to use, especially if you're comfortable with SQL. You can customize it to do what you need. Many other tools have started to use features similar to those introduced by StreamSets, like automated workflows that are easy to set up."
"StreamSets data drift feature gives us an alert upfront so we know that the data can be ingested. Whatever the schema or data type changes, it lands automatically into the data lake without any intervention from us, but then that information is crucial to fix for downstream pipelines, which process the data into models, like Tableau and Power BI models. This is actually very useful for us. We are already seeing benefits. Our pipelines used to break when there were data drift changes, then we needed to spend about a week fixing it. Right now, we are saving one to two weeks. Though, it depends on the complexity of the pipeline, we are definitely seeing a lot of time being saved."
"It is really easy to set up and the interface is easy to use."
 

Cons

"It requires some application specific connectors which are lacking. This needs to be added."
"We continuously face issues, such as Kafka being down and slow responses from the support team."
"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."
"It would help if the knowledge based documents in the support portal could be available for public use as well."
"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"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."
"It could have more integration with different platforms."
"It could have more themes. They should also have more reporting-oriented plugins as well. It would be great to have free custom reports that can be dispatched directly from Jira."
"The logging mechanism could be improved. If I am working on a pipeline, then create a job out of it and it is running, it will generate constant logs. So, the logging mechanism could be simplified. Now, it is a bit difficult to understand and filter the logs. It takes some time."
"Sometimes, it is not clear at first how to set up nodes. A site with an explanation of how each node works would be very helpful."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"In terms of the product, I don't think there is any room for improvement because it is very good. One small area of improvement that is very much needed is on the knowledge base side. Sometimes, it is not very clear how to set up a certain process or a certain node for a person who's using the platform for the first time."
"StreamSets should provide a mechanism to be able to perform data quality assessment when the data is being moved from one source to the target."
"I would like to see it integrate with other kinds of platforms, other than Java. We're going to have a lot of applications using .NET and other languages or frameworks. StreamSets is very helpful for the old Java platform but it's hard to integrate with the other platforms and frameworks."
"One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infrastructure."
 

Pricing and Cost Advice

"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"Confluent is an expensive solution."
"You have to pay additional for one or two features."
"The solution is cheaper than other products."
"Confluence's pricing is quite reasonable, with a cost of around $10 per user that decreases as the number of users increases. Additionally, it's worth noting that for teams of up to 10 users, the solution is completely free."
"It comes with a high cost."
"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."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"It has a CPU core-based licensing, which works for us and is quite good."
"The overall cost is very flexible so it is not a burden for our organization... However, the cost should be improved. For small and mid-size organizations it might be a challenge."
"There are two editions, Professional and Enterprise, and there is a free trial. We're using the Professional edition and it is competitively priced."
"It's not so favorable for small companies."
"StreamSets Data Collector is open source. One can utilize the StreamSets Data Collector, but the Control Hub is the main repository where all the jobs are present. Everything happens in Control Hub."
"The pricing is affordable for any business."
"We use the free version. It's great for a public, free release. Our stance is that the paid support model is too expensive to get into. They should honestly reevaluate that."
"We are running the community version right now, which can be used free of charge."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
881,515 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
11%
Retailer
9%
Manufacturing Company
7%
Insurance Company
8%
Financial Services Firm
8%
Manufacturing Company
8%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise16
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise11
 

Questions from the Community

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 ...
What do you like most about StreamSets?
The best thing about StreamSets is its plugins, which are very useful and work well with almost every data source. It's also easy to use, especially if you're comfortable with SQL. You can customiz...
What needs improvement with StreamSets?
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infr...
What is your primary use case for StreamSets?
We are using StreamSets for batch loading.
 

Overview

 

Sample Customers

ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about Confluent vs. StreamSets and other solutions. Updated: December 2025.
881,515 professionals have used our research since 2012.