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

Confluent vs Google Cloud Dataflow 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
7th
Average Rating
8.2
Reviews Sentiment
6.3
Number of Reviews
25
Ranking in other categories
No ranking in other categories
Google Cloud Dataflow
Ranking in Streaming Analytics
13th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
15
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Streaming Analytics category, the mindshare of Confluent is 6.4%, down from 8.3% compared to the previous year. The mindshare of Google Cloud Dataflow is 3.4%, down from 5.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Confluent6.4%
Google Cloud Dataflow3.4%
Other90.2%
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.
reviewer2812851 - PeerSpot reviewer
Senior Customer Data Platform Specialist at a marketing services firm with 1,001-5,000 employees
Unified user personas have improved data workflows and support detailed monitoring and logging
Google Cloud has many streams and products. In Google Cloud, everything is translated in the backend, so we do not have to use services such as Apache Beam. When you want to use Google Cloud Functions, you write the code, and the backend talks to all the libraries or Apache, so we do not need to be concerned about those. We just need to use our functions that translate and have many tools and services readily available. Google Cloud Dataflow has made it very easy for detailed monitoring and logging features for pipeline performance assessment. For example, if I am using Google Cloud Functions, I can easily see what changes I have done and trace it properly. I can see what is happening with this script, how many users are affected, whether the script is working, what is failing, and how we can rectify issues with proper monitoring.

Quotes from Members

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

Pros

"The documentation process is fast with the tool."
"The features I find most useful in Confluent are the Multi-Region Cluster, MRC, and the Cluster Linking for replication."
"To date, we have seen improvements in performance and scalability, so we recommend this solution."
"We ensure seamless management of Kafka through Confluent, allowing all of our Kafka activities to be handled by a third party."
"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."
"Confluence's greatest asset is its user-friendly interface, coupled with its remarkable ability to seamlessly integrate with a vast range of other solutions."
"Overall, it's a great company and they have excellent software."
"Having used SharePoint in the past, when I compare with traditional, old document repositories, like SharePoint, I would definitely recommend Confluent."
"The support team is good and it's easy to use."
"The most valuable features of Google Cloud Dataflow are scalability and connectivity."
"The service is relatively cheap compared to other batch-processing engines."
"I don't need a server running all the time while using the tool. It is also easy to setup. The product offers a pay-as-you-go service."
"It is a scalable solution."
"Google's support team is good at resolving issues, especially with large data."
"The solution allows us to program in any language we desire."
"The best feature of Google Cloud Dataflow is its practical connectedness."
 

Cons

"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."
"It requires some application specific connectors which are lacking. This needs to be added."
"They should remove Zookeeper because of security issues."
"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 product should integrate tools for incorporating diagrams like Lucidchart. It also needs to improve its formatting features. We also faced issues while granting permissions."
"The formatting aspect within the page can be improved and more powerful."
"There is no local support team in Saudi Arabia."
"The beginner who doesn't know how to work on HTML will struggle as when you create spaces in the Confluent, if you want to have some meeting notes or anything else, you need to know HTML and which HTML tags to include."
"Occasionally, dealing with a huge volume of data causes failure due to array size."
"The solution's setup process could be more accessible."
"They should do a market survey and then make improvements."
"Google Cloud Data Flow can improve by having full simple integration with Kafka topics. It's not that complicated, but it could improve a bit. The UI is easy to use but the experience could be better. There are other tools available that do a better job."
"Promoting the technology more broadly would help increase its adoption."
"The technical support has slight room for improvement."
"Currently, not all error logs are available to users and this could make debugging failed jobs very difficult."
"The deployment time could also be reduced."
 

Pricing and Cost Advice

"You have to pay additional for one or two features."
"It comes with a high cost."
"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"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."
"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 highly priced."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"On a scale from one to ten, where one is cheap, and ten is expensive, I rate the solution's pricing a seven to eight out of ten."
"The solution is not very expensive."
"The price of the solution depends on many factors, such as how they pay for tools in the company and its size."
"On a scale from one to ten, where one is cheap, and ten is expensive, I rate Google Cloud Dataflow's pricing a four out of ten."
"The tool is cheap."
"Google Cloud is slightly cheaper than AWS."
"Google Cloud Dataflow is a cheap solution."
"The solution is cost-effective."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Retailer
12%
Computer Software Company
8%
Manufacturing Company
6%
Financial Services Firm
18%
Manufacturing Company
13%
Retailer
8%
Comms Service Provider
7%
 

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 Business3
Midsize Enterprise2
Large Enterprise12
 

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 is your experience regarding pricing and costs for Google Cloud Dataflow?
Pricing is normal. It is part of a package received from Google, and they are not charging us too high.
What needs improvement with Google Cloud Dataflow?
I feel there could be something that they can introduce, such as when we have data in the tables, a feature that creates a unique persona of the user automatically, so we do not have to do that man...
What is your primary use case for Google Cloud Dataflow?
The primary use case for Google Cloud Dataflow is when a brand has a lot of data and wants to store it in their warehouse. They can use BigQuery to store their data or use big data solutions to sto...
 

Also Known As

No data available
Google Dataflow
 

Overview

 

Sample Customers

ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Absolutdata, Backflip Studios, Bluecore, Claritics, Crystalloids, Energyworx, GenieConnect, Leanplum, Nomanini, Redbus, Streak, TabTale
Find out what your peers are saying about Confluent vs. Google Cloud Dataflow and other solutions. Updated: June 2026.
908,800 professionals have used our research since 2012.