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

Confluent vs Spring Cloud Data Flow 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

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
Spring Cloud Data Flow
Ranking in Streaming Analytics
14th
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
9
Ranking in other categories
Data Integration (31st)
 

Mindshare comparison

As of April 2026, in the Streaming Analytics category, the mindshare of Confluent is 6.5%, down from 8.6% compared to the previous year. The mindshare of Spring Cloud Data Flow is 3.1%, down from 4.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Confluent6.5%
Spring Cloud Data Flow3.1%
Other90.4%
Streaming Analytics
 

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.
NitinGoyal - PeerSpot reviewer
Engineering Lead at Naukri.com
Has a plug-and-play model and provides good robustness and scalability
The solution's community support could be improved. I don't know why the Spring Cloud Data Flow community is not very strong. Community support is very limited whenever you face any problem or are stuck somewhere. I'm not sure whether it has improved in the last six months because this pipeline was set up almost two years ago. I struggled with that a lot. For example, there was limited support whenever I got an exception and sought help from Stack Overflow or different forums. Interacting with Kubernetes needs a few certificates. You need to define all the certificates within your application. With the help of those certificates, your Java application or Spring Cloud Data Flow can interact with Kubernetes. I faced a lot of hurdles while placing those certificates. Despite following the official documentation to define all the replicas, readiness, and liveliness probes within the Spring Cloud Data Flow application, it was not working. So, I had to troubleshoot while digging in and debugging the internals of Spring Cloud Data Flow at that time. It was just a configuration mismatch, and I was doing nothing weird. There was a small spelling difference between how Spring Cloud Data Flow was expecting it and how I passed it. I was just following the official documentation.

Quotes from Members

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

Pros

"As an enterprise organization, data availability is critical and Confluent provides that SLA support."
"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 solution can handle a high volume of data because it works and scales well."
"We ensure seamless management of Kafka through Confluent, allowing all of our Kafka activities to be handled by a third party."
"Our main goal is to validate whether we can build a scalable and cost-efficient way to replicate data from these various sources."
"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."
"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 most valuable features of Spring Cloud Data Flow are the simple programming model, integration, dependency Injection, and ability to do any injection. Additionally, auto-configuration is another important feature because we don't have to configure the database and or set up the boilerplate in the database in every project. The composability is good, we can create small workloads and compose them in any way we like."
"Overall, Spring Cloud Data Flow is a really good solution and a lot cheaper than a lot of infrastructure provided by big companies like Google or Amazon."
"The ease of deployment on Kubernetes, the seamless integration for orchestration of various pipelines, and the visual dashboard that simplifies operations even for non-specialists such as quality analysts."
"There are a lot of options in Spring Cloud. It's flexible in terms of how we can use it. It's a full infrastructure."
"The most valuable feature is real-time streaming."
"The most valuable feature is real-time streaming."
"The best thing I like about Spring Cloud Data Flow is its plug-and-play model."
"The product is very user-friendly."
 

Cons

"From the control center perspective, there is a lot of room for improvement in the visualization."
"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 could have more integration with different platforms."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"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."
"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"Spring Cloud Data Flow could improve the user interface. We can drag and drop in the application for the configuration and settings, and deploy it right from the UI, without having to run a CI/CD pipeline. However, that does not work with Kubernetes, it only works when we are working with jars as the Spring Cloud Data Flow applications."
"Some of the features, like the monitoring tools, are not very mature and are still evolving."
"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."
"The documentation on offer is not that good."
"I would improve the dashboard features as they are not very user-friendly."
"The visual user interface could use some help; it needs improvement."
"There were instances of deployment pipelines getting stuck, and the dashboard not always accurately showing the application status, requiring manual intervention such as rerunning applications or refreshing the dashboard."
"On the tool's online discussion forums, you may get stuck with an issue, making it an area where improvements are required."
 

Pricing and Cost Advice

"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."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"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."
"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."
"Confluent is highly priced."
"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."
"The solution provides value for money, and we are currently using its community edition."
"This is an open-source product that can be used free of charge."
"If you want support from Spring Cloud Data Flow there is a fee. The Spring Framework is open-source and this is a free solution."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
886,468 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Retailer
11%
Computer Software Company
10%
Manufacturing Company
5%
Financial Services Firm
18%
Computer Software Company
12%
Retailer
8%
Manufacturing Company
6%
 

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 Business3
Midsize Enterprise1
Large Enterprise5
 

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 needs improvement with Spring Cloud Data Flow?
There were instances of deployment pipelines getting stuck, and the dashboard not always accurately showing the application status, requiring manual intervention such as rerunning applications or r...
What is your primary use case for Spring Cloud Data Flow?
We had a project for content management, which involved multiple applications each handling content ingestion, transformation, enrichment, and storage for different customers independently. We want...
What advice do you have for others considering Spring Cloud Data Flow?
I would definitely recommend Spring Cloud Data Flow. It requires minimal additional effort or time to understand how it works, and even non-specialists can use it effectively with its friendly docu...
 

Overview

 

Sample Customers

ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Information Not Available
Find out what your peers are saying about Confluent vs. Spring Cloud Data Flow and other solutions. Updated: March 2026.
886,468 professionals have used our research since 2012.