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

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 (9th)
StreamSets
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
Data Integration (22nd)
 

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.6%, down 8.3% 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 Mindshare Distribution
ProductMindshare (%)
Confluent6.6%
Apache Flink8.2%
Databricks7.9%
Other77.3%
Streaming Analytics
Data Integration Mindshare Distribution
ProductMindshare (%)
StreamSets1.2%
Informatica Intelligent Data Management Cloud (IDMC)3.7%
SSIS3.6%
Other91.5%
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

"Confluent is an amazing tool that is highly configurable, integrates very well with Jira, and lets you create nice documentation for various products while also supporting reporting and online content hosting."
"We primarily use Confluent for service desk and task management, and it is also good for knowledge base management."
"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."
"Implementing Confluent's schema registry has significantly enhanced our organization's data quality assurance."
"The biggest benefit of Confluent as a tool is that it is a distributed platform that provides more durability and stability."
"We ensure seamless management of Kafka through Confluent, allowing all of our Kafka activities to be handled by a third party."
"The features I find most useful in Confluent are the Multi-Region Cluster, MRC, and the Cluster Linking for replication."
"Some of the best features are that it's very quick to set up, very easy to have a centralized area that gives us a history of changes, and the ability to give feedback on any information placed onto the pages."
"StreamSets' reusable assets have helped to reduce workload by 32% to 40%."
"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."
"StreamSets Transformer is a good feature because it helps you when you are developing applications and when you don't want to write a lot of code. That is the best feature overall."
"It is really easy to set up and the interface is easy to use."
"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 has definitely helped us in getting the information into our data lake very quickly, in terms of ingestion, and the most important thing is it has helped us from a resourcing point of view because you can easily upskill a BI or ETL resource without any programming knowledge to work with this, which has drastically reduced the time that we are spending on workloads by 60% to 70% as well as reducing the time spent on ingestion by 30%."
"The ETL capabilities are very useful for us. We extract and transform data from multiple data sources, into a single, consistent data store, and then we put it in our systems. We typically use it to connect our Apache Kafka with data lakes. That process is smooth and saves us a lot of time in our production systems."
"The scheduling within the data engineering pipeline is very much appreciated, and it has a wide range of connectors for connecting to any data sources like SQL Server, AWS, Azure, etc. We have used it with Kafka, Hadoop, and Azure Data Factory Datasets. Connecting to these systems with StreamSets is very easy."
 

Cons

"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."
"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."
"There is no local support team in Saudi Arabia."
"Confluence could improve the server version of the solution. However, most companies are going to the cloud."
"The product should integrate tools for incorporating diagrams like Lucidchart. It also needs to improve its formatting features. We also faced issues while granting permissions."
"It requires some application specific connectors which are lacking. This needs to be added."
"It could be more user-friendly and centralized. A way to reduce redundancy would be helpful."
"The solution could have an extra plugin or upgrading feature. In addition, it could have more integration with different platforms and be more compatible."
"The design experience is the bane of our existence because their documentation is not the best. Even when they update their software, they don't publish the best information on how to update and change your pipeline configuration to make it conform to current best practices. We don't pay for the added support. We use the "freeware version." The user community, as well as the documentation they provide for the standard user, are difficult, at best."
"One area for improvement could be the cloud storage server speed, as we have faced some latency issues here and there."
"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."
"The software is very good overall. Areas for improvement are the error logging and the version history. I would like to see better, more detailed error logging information."
"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."
"StreamSet works great for batch processing but we are looking for something that is more real-time. We need latency in numbers below milliseconds."
"We create pipelines or jobs in StreamSets Control Hub. It is a great feature, but if there is a way to have a folder structure or organize the pipelines and jobs in Control Hub, it would be great. I submitted a ticket for this some time back."
"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."
 

Pricing and Cost Advice

"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."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"The solution is cheaper than other products."
"Confluent is highly priced."
"Confluent is an expensive solution."
"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."
"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 has a CPU core-based licensing, which works for us and is quite good."
"There are different versions of the product. One is the corporate license version, and the other one is the open-source or free version. I have been using the corporate license version, but they have recently launched a new open-source version so that anybody can create an account and use it. The licensing cost varies from customer to customer. I don't have a lot of input on that. It is taken care of by PMO, and they seem fine with its pricing model. It is being used enterprise-wide. They seem to have got a good deal for StreamSets."
"It's not so favorable for small companies."
"Its pricing is pretty much up to the mark. For smaller enterprises, it could be a big price to pay at the initial stage of operations, but the moment you have the Seed B or Seed C funding and you want to scale up your operations and aren't much worried about the funds, at that point in time, you would need a solution that could be scaled."
"I believe the pricing is not equitable."
"The licensing is expensive, and there are other costs involved too. I know from using the software that you have to buy new features whenever there are new updates, which I don't really like. But initially, it was very good."
"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."
"StreamSets is an expensive solution."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
899,258 professionals have used our research since 2012.
 

Top Industries

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

Company Size

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

Questions from the Community

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...
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.
What advice do you have for others considering StreamSets?
If asked, I definitely recommend StreamSets to other users. My overall rating for the solution is nine.
 

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 Databricks, Microsoft, Apache and others in Streaming Analytics. Updated: June 2026.
899,258 professionals have used our research since 2012.