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

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
3rd
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
22
Ranking in other categories
No ranking in other categories
Spring Cloud Data Flow
Ranking in Streaming Analytics
9th
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
9
Ranking in other categories
Data Integration (23rd)
 

Mindshare comparison

As of February 2025, in the Streaming Analytics category, the mindshare of Confluent is 8.5%, down from 11.6% compared to the previous year. The mindshare of Spring Cloud Data Flow is 4.9%, up from 4.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics
 

Featured Reviews

Yantao Zhao - PeerSpot reviewer
Great tool for sharing knowledge, internal communication and allows for real-time collaboration on pages
Confluence is easy to use and modify. However, sometimes there are too many pages. We have to reorganize the folder or parent account. Since everyone can create a page, the same knowledge might be created in multiple places by different people. This leads to redundancy and makes it difficult to find information. It's not centralized. So it could be more user-friendly and centralized. A way to reduce redundancy would be helpful. It's very easy to use, so everyone can create knowledge. But it would be good to synchronize and organize that information a bit better. Another improvement would be in Confluence search. You can search for keywords, but it's not like AI, not even ChatGPT or OpenAI. It would be nice to get more relevant or organized answers. If you're outside the company, you just get some titles containing the keyword you input. But if Confluence were like a database, you could input something and get a well-organized search offering from multiple pages.
NitinGoyal - PeerSpot reviewer
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

"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."
"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
"Our main goal is to validate whether we can build a scalable and cost-efficient way to replicate data from these various sources."
"The monitoring module is impressive."
"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."
"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."
"Their tech support is amazing; they are very good, both on and off-site."
"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."
"The best thing I like about Spring Cloud Data Flow is its plug-and-play model."
"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 solution's most valuable feature is that it allows us to use different batch data sources, retrieve the data, and then do the data processing, after which we can convert and store it in the target."
"The product is very user-friendly."
"The dashboards in Spring Cloud Dataflow are quite valuable."
"The most valuable feature is real-time streaming."
"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."
 

Cons

"Confluent's price needs improvement."
"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."
"They should remove Zookeeper because of security issues."
"there is room for improvement in the visualization."
"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."
"It could be more user-friendly and centralized. A way to reduce redundancy would be helpful."
"The pricing model should include the ability to pick features and be charged for them only."
"It would help if the knowledge based documents in the support portal could be available for public use as well."
"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."
"On the tool's online discussion forums, you may get stuck with an issue, making it an area where improvements are required."
"Spring Cloud Data Flow is not an easy-to-use tool, so improvements are required."
"The solution's community support could be improved."
"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."
"Some of the features, like the monitoring tools, are not very mature and are still evolving."
"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."
"I would improve the dashboard features as they are not very user-friendly."
 

Pricing and Cost Advice

"You have to pay additional for one or two features."
"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."
"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 is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"Confluent is highly priced."
"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 has a yearly license, which is a bit high because it's on a per-user basis."
"It comes with a high cost."
"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."
"The solution provides value for money, and we are currently using its community edition."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
832,138 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
17%
Manufacturing Company
8%
Insurance Company
5%
Financial Services Firm
27%
Computer Software Company
18%
Manufacturing Company
7%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
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 maintenanc...
What needs improvement with Confluent?
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 c...
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: January 2025.
832,138 professionals have used our research since 2012.