Confluent vs StreamSets comparison

The compared Confluent and IBM solutions aren't in the same category. Confluent is ranked #3 in SA , with an average rating of 7.8, and holds a 7.8% mindshare in the category. IBM is ranked #23 in DI , with an average rating of 9.0, and holds a 1.3% mindshare. Additionally, 95% of Confluent users are willing to recommend the solution, compared to 100% of IBM users who would recommend it.

Confluent

Read 25 Confluent reviews

4,722 Views
2,550 Comparison Views

95% willing to recommend

StreamSets

Read 21 StreamSets reviews

2,571 Views
1,877 Comparison Views

100% willing to recommend

Confluent

StreamSets

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between Confluent and StreamSets based on real PeerSpot user reviews.

Find out in this report how the two Streaming Analytics solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.

To learn more, read our detailed Confluent vs. StreamSets Report (Updated: September 2025).

Buyer's Guide

Confluent vs. StreamSets

September 2025

Download the complete report

Helped 872,869 peers since 2012

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

Ranking in other categories

Streaming Analytics (3rd)

StreamSets

Average Rating

8.4

Reviews Sentiment

7.0

Number of Reviews

Ranking in other categories

Data Integration (23rd)

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 7.8%, down 9.3% compared to last year.
StreamSets, on the other hand, focuses on Data Integration, holds 1.3% mindshare, down 1.6% since last year.

Streaming Analytics Market Share Distribution
Product	Market Share (%)
Confluent	7.8%
Apache Flink	14.4%
Databricks	11.8%
Other	66.0%

Streaming Analytics

Data Integration Market Share Distribution
Product	Market Share (%)
StreamSets	1.3%
Informatica PowerCenter	5.3%
SSIS	5.1%
Other	88.3%

Data Integration

Featured Reviews

PavanManepalli

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.

Read full review

Ved Prakash Yadav

Senior Data Platform Manager at a manufacturing company with 10,001+ employees

Useful for data transformation and helps with column encryption

We use various tools and alerting systems to notify us of pipeline errors or failures. StreamSets supports data governance and compliance by allowing us to encrypt incoming data based on specified rules. We can easily encrypt columns by providing the column name and hash key. If you're considering using StreamSets for the first time, I would advise first understanding why you want to use it and how it will benefit you. If you're dealing with change tracking or handling large amounts of data, it could be cost-effective compared to services like Amazon. It's easy to schedule and manage tasks with the tool, and you can enhance your skills as an ETL developer. You can easily migrate traditional pipelines built on platforms like Informatica or Talend to StreamSets. I rate the overall solution an eight out of ten.

Read full review

Quotes from Members

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

Pros

"The design of the product is extremely well built and it is highly configurable."

"The solution can handle a high volume of data because it works and scales well."

"The documentation process is fast with the tool."

"The client APIs are the most valuable feature."

"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."

"The features I find most useful in Confluent are the Multi-Region Cluster, MRC, and the Cluster Linking for replication."

"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."

"It is also good for knowledge base management."

More Confluent pros

"For me, the most valuable features in StreamSets have to be the Data Collector and Control Hub, but especially the Data Collector. That feature is very elegant and seamlessly works with numerous source systems."

"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 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."

"I have used Data Collector, Transformer, and Control Hub products from StreamSets. What I really like about these products is that they're very user-friendly. People who are not from a technological or core development background find it easy to get started and build data pipelines and connect to the databases. They would be comfortable like any technical person within a couple of weeks."

"The most valuable would be the GUI platform that I saw. I first saw it at a special session that StreamSets provided towards the end of the summer. I saw the way you set it up and how you have different processes going on with your data. The design experience seemed to be pretty straightforward to me in terms of how you drag and drop these nodes and connect them with arrows."

"The ability to have a good bifurcation rate and fewer mistakes is valuable."

"The Ease of configuration for pipes is amazing. It has a lot of connectors. Mainly, we can do everything with the data in the pipe. I really like the graphical interface too"

More StreamSets pros

Cons

"The formatting aspect within the page can be improved and more powerful."

"Confluence could improve the server version of the solution. However, most companies are going to the cloud."

"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."

"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."

"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."

"Confluent has fallen behind in being the tool of the industry. It's taking second place to things such as Word and SharePoint and other office tools that are more dynamic and flexible than 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."

"We continuously face issues, such as Kafka being down and slow responses from the support team."

More Confluent cons

"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."

"Currently, we can only use the query to read data from SAP HANA. What we would like to see, as soon as possible, is the ability to read from multiple tables from SAP HANA. That would be a really good thing that we could use immediately. For example, if you have 100 tables in SQL Server or Oracle, then you could just point it to the schema or the 100 tables and ingestion information. However, you can't do that in SAP HANA since StreamSets currently is lacking in this. They do not have a multi-table feature for SAP HANA. Therefore, a multi-table origin for SAP HANA would be helpful."

"There aren't enough hands-on labs, and debugging is also an issue because it takes a lot of time. Logs are not that clear when you are debugging, and you can only select a single source for a pipeline."

"StreamSet works great for batch processing but we are looking for something that is more real-time. We need latency in numbers below milliseconds."

"They need to improve their customer care services. Sometimes it has taken more than 48 hours to resolve an issue. That should be reduced. They are aware of small or generic issues, but not the more technical or deep issues. For those, they require some time, generally 48 to 72 hours to respond. That should be improved."

"One thing that I would like to add is the ability to manually enter data. The way the solution currently works is we don't have the option to manually change the data at any point in time. Being able to do that will allow us to do everything that we want to do with our data. Sometimes, we need to manually manipulate the data to make it more accurate in case our prior bifurcation filters are not good. If we have the option to manually enter the data or make the exact iterations on the data set, that would be a good thing."

"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."

"We've seen a couple of cases where it appears to have a memory leak or a similar problem."

More StreamSets cons

Pricing and Cost Advice

"You have to pay additional for one or two features."

"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."

"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."

"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."

"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."

"It comes with a high cost."

"Confluent is highly priced."

More Confluent pricing and cost advice

"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."

"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 too fixed. It should be based on how much data you need to process. Some businesses are not so big that they process a lot of data."

"It has a CPU core-based licensing, which works for us and is quite 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."

"The pricing is affordable for any business."

"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."

"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."

More StreamSets pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.

See recommendations

872,869 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

17%

Computer Software Company

12%

Retailer

Manufacturing Company

Computer Software Company

10%

Financial Services Firm

10%

Insurance Company

Manufacturing Company

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	6
Midsize Enterprise	4
Large Enterprise	16

By reviewers
Company Size	Count
Small Business	9
Midsize Enterprise	2
Large Enterprise	11

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...

See all answers

What is your experience regarding pricing and costs for Confluent?

They charge a lot for scaling, which makes it expensive.

See all answers

What needs improvement with Confluent?

See all answers

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...

See all answers

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...

See all answers

What is your primary use case for StreamSets?

We are using StreamSets for batch loading.

See all answers

Comparisons

Apache Flink vs Confluent

Compared 13% of the time

Amazon Kinesis vs Confluent

Compared 12% of the time

Databricks vs Confluent

Compared 8% of the time

Amazon MSK vs Confluent

Compared 6% of the time

AWS Glue vs Confluent

Compared 5% of the time

More Confluent Competitors

Informatica PowerCenter vs StreamSets

Compared 10% of the time

webMethods.io vs StreamSets

Compared 8% of the time

Qlik Replicate vs StreamSets

Compared 6% of the time

Oracle GoldenGate vs StreamSets

Compared 6% of the time

IBM InfoSphere DataStage vs StreamSets

Compared 6% of the time

More StreamSets Competitors

Product Reports

Buyer's Guide

Confluent

November 2025

Download Confluent product report

Buyer's Guide

StreamSets

October 2025

Download StreamSets product report

Overview

Confluent is an enterprise-ready, full-scale streaming platform that enhances Apache Kafka.

Confluent has integrated cutting-edge features that are designed to enhance these tasks:

Speed up application development and connectivity
Enable transformations through stream processing
Streamline business operations at scale
Adhere to strict architectural standards

Confluent is a more complete distribution of Kafka in that it enhances the integration possibilities of Kafka by introducing tools for managing and optimizing Kafka clusters while providing methods for making sure the streams are secure. Confluent supports publish-and-subscribe as well as the storing and processing of data within the streams. Kafka is easier to operate and build thanks to Confluent.

Confluent's software is available in three different varieties:

A free, open-source streaming platform that makes it simple to start using real-time data streams
An enterprise-grade version of the product with more administrative, ops, and monitoring tools
A premium cloud-based version.

Confluent Advantage Features

Confluent has many valuable key features. Some of the most useful ones include:

Multi-language
- Clients: C++, Python, Go, and .NET
- REST proxy: Can connect to Kafka from any connected network device
- Admin REST APIs: RESTful interface for performing administrator operations

Pre-built ecosystem
- Connectors: More than 100 supported connectors, including S3, Elastic, HDFS, JDBC
- MQTT proxy: Gain access to Kafka from MQTT gateways and devices
- Schema registry: Centralized database to guarantee data compatibility

Streaming database
- ksqlDB: Materialized views and real-time stream processing

GUI management
- Control panel: GUI for scalable Kafka management and monitoring
- Health+: Smart alerts and cloud-based control centers

DevOps automation that is flexible
- Confluent for Kubernetes: Complete API to deploy on Kubernetes
- Automated Ansible deployment on non-containerized environments

Dynamic performance
- Self-balancing clusters: Automated partition re-balancing across brokers in the cluster
- Tiered storage: Older Kafka data offloading to object storage with transparent access

Security that is enterprise-grade
- Role-based access control: Granular user/group access authorization
- Audit logs that are structured: Logs of user actions kept in dedicated Kafka topics
- Secret protection: Sensitive information is encrypted

Global resilience
- Linking clusters: A real-time, highly reliable, and consistent bridge across on-premises and cloud environments
- Multiple-region clusters: Single Kafka cluster with automated client failover distributed across multiple data centers
- Replicator: Asynchronous replication that is based on the Kafka Connect framework

Support
- Round the clock enterprise support from Kafka experts

Reviews from Real Users

Confluent stands out among its competitors for a number of reasons. Two major ones are its robust enterprise support and its open source option. PeerSpot users take note of the advantages of these features in their reviews:

Ravi B., a solutions architect at a tech services company, writes of the solution, “KSQL is a valuable feature, as is the Kafka Connect framework for connecting to the various source systems where you need not write the code. We get great support from Confluent because we're using the enterprise version and whenever there's a problem, they support us with fine-tuning and finding the root cause.”

Amit S., an IT consultant, notes, “The biggest benefit is that it is open source. You have the flexibility of opting or not opting for enterprise support, even though the tool itself is open source.” He adds, “The second benefit is it's very modern and built on Java and Scala. You can extend the features very well, and it doesn't take a lot of effort to do so.”

Confluent

StreamSets is a data integration platform that enables organizations to efficiently move and process data across various systems. It offers a user-friendly interface for designing, deploying, and managing data pipelines, allowing users to easily connect to various data sources and destinations. StreamSets also provides real-time monitoring and alerting capabilities, ensuring that data is flowing smoothly and any issues are quickly addressed.

IBM

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

Buyer's Guide

Confluent vs. StreamSets

September 2025

Free Report: Confluent vs. StreamSets

Find out what your peers are saying about Confluent vs. StreamSets and other solutions. Updated: September 2025.

DOWNLOAD NOW

872,869 professionals have used our research since 2012.

See our Confluent vs. StreamSets report.

We monitor all Streaming Analytics reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.