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

Cloudera DataFlow vs Databricks 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

Cloudera DataFlow
Ranking in Streaming Analytics
19th
Average Rating
7.4
Reviews Sentiment
6.5
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Databricks
Ranking in Streaming Analytics
1st
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
94
Ranking in other categories
Cloud Data Warehouse (4th), Data Science Platforms (1st), Data Management Platforms (DMP) (5th)
 

Mindshare comparison

As of June 2026, in the Streaming Analytics category, the mindshare of Cloudera DataFlow is 2.0%, up from 1.1% compared to the previous year. The mindshare of Databricks is 7.9%, down from 14.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Databricks7.9%
Cloudera DataFlow2.0%
Other90.1%
Streaming Analytics
 

Featured Reviews

Mohamed-Saied - PeerSpot reviewer
Senior Data Architect at Teradata Corporation
Efficient data integration and workflow scheduling elevate project performance
Cloudera DataFlow is used as an ETL or ELT solution within Cloudera's data pipeline. Our organization heavily relies on it for data ingestion, transformation, and warehousing. It is also used daily for operational tasks, and it integrates well within Cloudera's ecosystem for high performance and…
SimonRobinson - PeerSpot reviewer
Governance And Engagement Lead
Improved data governance has enabled sensitive data tracking but cost management still needs work
I believe we could improve Databricks integration with cloud service providers. The impact of our current integration has not been particularly good, and it's becoming very expensive for us. The inefficiencies in our implementation, such as not shutting down warehouses when they're not in use or reserving the right number of credits, have led to increased costs. We made several beginner mistakes, such as not taking advantage of incremental loading and running overly complicated queries all the time. We should be using ETL tools to help us instead of doing it directly in Databricks. We need more experienced professionals to manage Databricks effectively, as it's not as forgiving as other platforms such as Snowflake. I think introducing customer repositories would facilitate easier implementation with Databricks.

Quotes from Members

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

Pros

"DataFlow's performance is okay."
"The initial setup was not so difficult"
"Cloudera DataFlow is fully compatible with Cloudera's ecosystem and offers high efficiency through native connectors for various ecosystems."
"This solution is very scalable and robust."
"The most effective features are data management and analytics."
"The Delta Lake data type has been the most useful part of this solution. Delta Lake is an opensource data type and it was implemented and invented by Databricks."
"I like how easy it is to share your notebook with others. You can give people permission to read or edit. I think that's a great feature. You can also pull in code from GitHub pretty easily. I didn't use it that often, but I think that's a cool feature."
"It is a cost-effective solution."
"Databricks allowed us to go from non-existent insights (because the datasets were just too large) to immediate and rich insights once the datasets were ingested into our PySpark notebooks."
"A very valuable feature is the data processing, and the solution is specifically good at using the Spark ecosystem."
"The most valuable feature is the versatility of the ecosystem."
"The capability of the product is quite good and we are very satisfied with it overall."
"Specifically for data science and data analytics purposes, it can handle large amounts of data in less time. I can compare it with Teradata. If a job takes five hours with Teradata databases, Databricks can complete it in around three to three and a half hours."
 

Cons

"Although their workflow is pretty neat, it still requires a lot of transformation coding; especially when it comes to Python and other demanding programming languages."
"It's an outdated legacy product that doesn't meet the needs of modern data analysts and scientists."
"It is not easy to use the R language. Though I don't know if it's possible, I believe it is possible, but it is not the best language for machine learning."
"Cloudera DataFlow's UI interface could be enhanced significantly. Memory handling can also be improved to be better than it is today."
"I would like to see more documentation in terms of how an end-user could use it, and users like me can easily try it and implement use cases."
"The solution has some scalability and integration limitations when consolidating legacy systems."
"I think setting up the whole account for one person and giving access are areas that can be difficult to manage and should be made a little easier."
"I think the automatic categorization of variables needs to be improved; the current functionality is not always efficiently identifying the features of the data that is collected."
"When I used the support, I had communication problems because of the language barrier with the agent. The accent was difficult to understand."
"Databricks' performance when serving the data to an analytics tool isn't as good as Snowflake's."
"The solution could be improved by adding a feature that would make it more user-friendly for our team. The feature is simple, but it would be useful. Currently, our team is more familiar with the language R, but Databricks requires the use of Jupyter Notebooks which primarily supports Python. We have tried using RStudio, but it is not a fully integrated solution. To fully utilize Databricks, we have to use the Jupyter interface. One feature that would make it easier for our team to adopt the Jupyter interface would be the ability to select a specific variable or line of code and execute it within a cell. This feature is available in other Jupyter Notebooks outside of Databricks and in our own IDE, but it is not currently available within Databricks. If this feature were added, it would make the transition to using Databricks much smoother for our team."
"The solution is not exactly stable. We've faced a few bugs which have really affected it, especially when it comes to connecting with Spark."
 

Pricing and Cost Advice

"DataFlow isn't expensive, but its value for money isn't great."
"The licensing costs of Databricks depend on how many licenses we need, depending on which Databricks provides a lot of discounts."
"Price-wise, I would rate Databricks a three out of five."
"Licensing on site I would counsel against, as on-site hardware issues tend to really delay and slow down delivery."
"The billing of Databricks can be difficult and should improve."
"The solution requires a subscription."
"The licensing costs of Databricks is a tiered licensing regime, so it is flexible."
"Databricks uses a price-per-use model, where you can use as much compute as you need."
"We have only incurred the cost of our AWS cloud services. This is because during this period, Databricks provided us with an extended evaluation period, and we have not spent much money yet. We are just starting to incur costs this month, I will know more later on the full cost perspective."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Construction Company
14%
Manufacturing Company
10%
Comms Service Provider
8%
Financial Services Firm
18%
Manufacturing Company
10%
Computer Software Company
7%
Healthcare Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business27
Midsize Enterprise12
Large Enterprise57
 

Questions from the Community

What needs improvement with Cloudera DataFlow?
Cloudera DataFlow's UI interface could be enhanced significantly. Memory handling can also be improved to be better than it is today.
What is your primary use case for Cloudera DataFlow?
Cloudera DataFlow is used as an ETL or ELT solution within Cloudera's data pipeline. Our organization heavily relies on it for data ingestion, transformation, and warehousing. It is also used daily...
What advice do you have for others considering Cloudera DataFlow?
Cloudera DataFlow is fully compatible with Cloudera's ecosystem and offers high efficiency through native connectors for various ecosystems. However, the learning curve is high, and there is a shor...
Which do you prefer - Databricks or Azure Machine Learning Studio?
Databricks gives you the option of working with several different languages, such as SQL, R, Scala, Apache Spark, or Python. It offers many different cluster choices and excellent integration with ...
How would you compare Databricks vs Amazon SageMaker?
We researched AWS SageMaker, but in the end, we chose Databricks. Databricks is a Unified Analytics Platform designed to accelerate innovation projects. It is based on Spark so it is very fast. It...
Which would you choose - Databricks or Azure Stream Analytics?
Databricks is an easy-to-set-up and versatile tool for data management, analysis, and business analytics. For analytics teams that have to interpret data to further the business goals of their orga...
 

Comparisons

 

Also Known As

CDF, Hortonworks DataFlow, HDF
Databricks Unified Analytics, Databricks Unified Analytics Platform, Redash
 

Overview

 

Sample Customers

Clearsense
Elsevier, MyFitnessPal, Sharethrough, Automatic Labs, Celtra, Radius Intelligence, Yesware
Find out what your peers are saying about Cloudera DataFlow vs. Databricks and other solutions. Updated: June 2026.
900,644 professionals have used our research since 2012.