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 (16th), Business Performance Management (16th), Reporting (7th), Data Visualization (8th)
Spring Cloud Data Flow
Ranking in Data Integration
22nd
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
9
Ranking in other categories
Streaming Analytics (9th)
 

Mindshare comparison

As of May 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.1%, 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

"One feature which I have found to be very interesting is the Beast manager, where you can create calculated fields. They are shared in one common repository so someone else can use the same calculated fields; they don't have to rewrite or reinvent the APIs."
"The dashboarding itself was pretty easy. So both the front and the back end were positive in this case."
"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 fact that you can add any data source is valuable. The entire data handling suite they have, all the apps, etc., is pretty amazing. One of the key things, not being a techie or a data-warehouse guy, is that you can connect data sources, and do all kinds of pretty amazing things."
"I mostly see it as an ETL which has many system connectors. It does a good job of ETL."
"We have found securing data valuable because it allows us to provide information without identifying individuals."
"The pipeline features and data ingestions in Domo are quite good."
"This solution allows us to change our performance metrics and tracks our goals in real-time."
"The most valuable feature is real-time streaming."
"The dashboards in Spring Cloud Dataflow are quite valuable."
"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 product is very user-friendly."
"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 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 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."
 

Cons

"When you're exporting a graph out of Domo — suppose it is in the form of a donut chart or it is in form of a stack — the data comes out in tabular format, not as a graph. When exporting the data, I would like them to create a tab for graphs and another tab with the data in tabular format."
"It's too early for me to say that something needs improvement, but there are times when there have been some flexibility issues with Domo... Tableau has a window function which can be integrated into a calculated field. That is missing in Domo so you have to make changes to the data set using ETL or SQL."
"There were very few cases on some of the tables, the data tables, where I wish there was an additional feature or two."
"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."
"It is expensive."
"One of the improvements that could be made is related to improved storage options."
"One of the biggest problems is that end users require a license to run their own reports and dashboards, which are fairly expensive."
"If Domo had a Copilot feature, you could interact with the graphs and talk to the graphs and tables."
"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."
"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."
"Spring Cloud Data Flow is not an easy-to-use tool, so improvements are required."
"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 solution's community support could be improved."
"I would improve the dashboard features as they are not very user-friendly."
"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."
 

Pricing and Cost Advice

"I believe that the investment in Domo was worthwhile because it allowed for the organization to jump in quickly, with little training. There are different plans available based on the requirements."
"The pricing differs from customer to customer, depending on the package."
"It started out at about $600 a seat. However, then as we started to grow, it scaled that down to about $330 or 3$50 a seat, if I'm not mistaken."
"They've built an "app economy." Some of them are really expensive, so they're not for startups and smaller companies. They're more like enterprise tools. We couldn't afford some of them, because they were so crazy expensive. But if I was working for a bank, insurance company, or some bigger corporation then, for sure, you could justify those prices... It was silly expensive back then and it probably still is, or even more expensive."
"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."
"Domo has more than one licensing model. You can choose between the yearly subscription and the per-user licensing model. The tool is flexible in terms of licensing. As for the cost, Domo is an end-to-end BI tool so its pricing is a little higher than other players in the market, for example, non end-to-end BI tools such as OBIEE and Tableau specific only for business intelligence and presenting data to the end users, unlike Domo which handles everything. You want to get Domo as an integration tool, an ETL tool, etc. As the tool is end-to-end, its cost is always going to be a little higher than other BI tools, but it's worth paying because you won't have to spend extra for other activities. After all, Domo can do those activities."
"It is on the pricier end."
"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 Data Integration solutions are best for your needs.
850,236 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
12%
University
10%
Manufacturing Company
8%
Financial Services Firm
7%
Financial Services Firm
27%
Computer Software Company
17%
Retailer
7%
Healthcare 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: April 2025.
850,236 professionals have used our research since 2012.