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

Domo vs Spring Cloud Data Flow comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 19, 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

Domo
Ranking in Data Integration
47th
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
37
Ranking in other categories
BI (Business Intelligence) Tools (14th), Business Performance Management (15th), Reporting (12th), Data Visualization (13th)
Spring Cloud Data Flow
Ranking in Data Integration
21st
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
9
Ranking in other categories
Streaming Analytics (9th)
 

Mindshare comparison

As of June 2025, in the Data Integration category, the mindshare of Domo is 0.5%, up from 0.0% compared to the previous year. The mindshare of Spring Cloud Data Flow is 1.2%, up from 0.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration
 

Featured Reviews

James John Wilson - PeerSpot reviewer
Robust, powerful, and easy to use
There were very few cases on some of the tables, the data tables, where I wish there was an additional feature or two. However, they were particular. What I wanted to see was the ability to collapse when you group a set of rows, let's say when you group them by status or health, so you have your red projects grouped up top. I wanted to compress or collapse that group of red and then open the yellow projects and then the green projects. There were a bit more features in the tables than I wanted to see. They have a widget that you can use either in Microsoft PowerPoint to pull over data into your PowerPoints and refresh graphs or charts or metrics or tables. I would love to see that available in Google Slides. I used it successfully in PowerPoint; however, at one company, they were only using Google products, and so that widget didn't help with reporting in slides. Therefore, we had to do a bit more manual work for our quarterly business reviews or monthly business reviews to produce our executive presentations. Sometimes the fonts were difficult to read if you're trying to put a lot of data in a table and show a lot of rows. Sometimes the fonts got too light, and you had to really play with it to try and figure out how to make it readable. One thing I had to do, and I don't know if it's necessarily a bad thing, was when I was running a meeting, I would have to go turn off the data jobs. If I was running a meeting and a lot of times people were scrambling in the background to do their updates even as the meeting was occurring, it would cause the page to render very slowly. It would sometimes pause or freeze. I found that if I went and turned off the status, the data update jobs that we're pulling data from Smartsheet, then the meetings would work more smoothly, and there were no interruptions or delays.
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

"The best thing is that the data storage is pretty much free. I can store as much data as I want, from different sources."
"The user interface is quite good."
"We've worked with all the features of Domo. Among the most important are Pivot and Sumo Cards. We can use drill-down from the top-most level with a click, generating charts."
"The most valuable feature currently is the self-service BI availability in Domo. I would say the data file fabric solutions where the users themselves are responsible for generating their own reports."
"The dashboard is the most valuable feature and allows for customization to create and share reports."
"In Workbench 5, they have come up with a very useful feature called Upsert. When you're pushing data into the data set, if the data is already available it will update the data, and if that the data is not there it will insert it. That is a beneficial feature that they introduced in the latest version."
"The ability to create custom connectors was useful because you never know, with customers, what platform they want to utilize or what data they have. It gave us a lot of flexibility in being able to bring data in from different places."
"In general, Domo is very powerful and very easy to use, relatively speaking."
"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 best thing I like about Spring Cloud Data Flow is its plug-and-play model."
"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 most valuable feature is real-time streaming."
"The product is very user-friendly."
"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 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."
"The dashboards in Spring Cloud Dataflow are quite valuable."
 

Cons

"If your ETL runs more than 24 hours, it always fails because we are logging a lot of historical data, and there is a restriction on the amount of data (in rows) that you can run. The technical support has not found a solution for this yet."
"Their organization or client service didn't always keep up... They took on more and more clients and the processes slowed down a little bit."
"One of the improvements that could be made is related to improved storage options."
"It is very difficult too, if we do have specific requests or errors that we can't get figure out - especially when it comes to the development platform, developing custom connectors or doing any kind of API work, custom cards - in that there's a lag in the response time."
"I would like to see more flexibility in their pricing structure. The trend is moving from database pricing to a user-license pricing model. That would be a benefit if they wanted to reevaluate their pricing structure."
"The forecasting feature, the regression features, and the Python libraries could all be improved. They're all in beta."
"In terms of the analytics, there is quite a limited set of options when using Domo. Whereas with Tableau we can perform heavy statistical computations, Domo doesn't have that capability. Domo is quite limited on that side."
"It is expensive."
"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."
"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."
"I would improve the dashboard features as they are not very user-friendly."
"Some of the features, like the monitoring tools, are not very mature and are still evolving."
"On the tool's online discussion forums, you may get stuck with an issue, making it an area where improvements are required."
"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 solution's community support could be improved."
"Spring Cloud Data Flow is not an easy-to-use tool, so improvements are required."
 

Pricing and Cost Advice

"No matter if you're a developer or an end-user, the licensing cost is around $12 per user per month."
"The pricing differs from customer to customer, depending on the package."
"I think it is reasonable."
"It is on the pricier end."
"Because it's software as a service, it's more expensive on the face of it. But there are a lot of variables. I don't have to pay for servers or for infrastructure. I don't have to pay labor for my IT organization to set up or maintain the environment. I don't have to pay for them to upgrade the software, and test it, etc., because when it rolls out, it is transparent and seamless for us. But, because of that, it costs more, I imagine, than Sisense, or Yellowfin, or Power BI. A lot of those make it sound like they're inexpensive, but when you add in all the hidden costs and all of the overhead, it's probably comparable."
"The solution is expensive compared to one of its competitors."
"We are making money from Domo, and all our clients are happy with the information that they receive from it."
"The price that they offered was around $200 per user license. It was pretty cheap at that time compared to other companies. I think they have revamped their pricing structure since then."
"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."
"This is an open-source product that can be used free of charge."
"The solution provides value for money, and we are currently using its community edition."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
859,438 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
12%
University
11%
Manufacturing Company
8%
Financial Services Firm
8%
Financial Services Firm
26%
Computer Software Company
17%
Retailer
7%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Domo?
All our client SLAs and daily and weekly dashboards are tracked on Domo.
What needs improvement with Domo?
One of the biggest problems is that end users require a license to run their own reports and dashboards, which are fairly expensive. Domo is also not the easiest product to use and is more expensiv...
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...
 

Also Known As

corda
No data available
 

Overview

 

Sample Customers

Capco, SABMiller, Stance, eBay, Sage North America, Goodwill Industries of Central Indiana, Telus, The Cliffs, OGIO International Inc., and many more!
Information Not Available
Find out what your peers are saying about Domo vs. Spring Cloud Data Flow and other solutions. Updated: June 2025.
859,438 professionals have used our research since 2012.