We performed a comparison between Domo and Pentaho Data Integration and Analytics based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The dashboard is the most valuable feature and allows for customization to create and share reports."
"Domo is not a difficult tool to learn. All you need to know is the SQL for the ETL part. You don't need to write much code. That's the great part. It uses legacy languages, like SQL, which is very common among developers who then don't have to go and learn Domo's own syntax. Therefore, you don't have to learn another hard language to use Domo."
"All our client SLAs and daily and weekly dashboards are tracked on Domo."
"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."
"I mostly see it as an ETL which has many system connectors. It does a good job of ETL."
"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 data certification feature, where the admin user can put a certified stamp on a data source so that other users can know that that is the correct and accurate data flow or data source to use, is a good feature."
"This solution allows us to change our performance metrics and tracks our goals in real-time."
"The way it has improved our product is by giving our users the ability to do ad hoc reports, which is very important to our users. We can do predictive analysis on trends coming in for contracts, which is what our product does. The product helps users decide which way to go based on the predictive analysis done by Pentaho. Pentaho is not doing predictions, but reporting on the predictions that our product is doing. This is a big part of our product."
"Flexible deployment, in any environment, is very important to us. That is the key reason why we ended up with these tools. Because we have a very highly secure environment, we must be able to install it in multiple environments on multiple different servers. The fact that we could use the same tool in all our environments, on-prem and in the cloud, was very important to us."
"It's my understanding that the product can scale."
"Provides a good open source option."
"The abstraction is quite good."
"It has a really friendly user interface, which is its main feature. The process of automating or combining SQL code with some databases and doing the automation is great and really convenient."
"We're using the PDI and the repository function, and they give us the ability to easily generate reporting and output, and to access data. We also like the ability to schedule."
"Data transformation within Pentaho is a nice feature that they have and that I value."
"It's quite slow. We are using about 2,000,000 rows of data. Creating certain reports takes almost a couple of minutes, which should not be the case."
"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."
"I would like to be able to drill down more when there is a particular area where there is a problem. I don't clearly see that in Domo at the moment."
"The forecasting feature, the regression features, and the Python libraries could all be improved. They're all in beta."
"I would also like to see improvements to their drag and drop Magic ETL tool. You can drag and drop your ETL tool, but it doesn't really work for a large amount of data. It struggles with that. In a real-world application, where you're working with 30 million rows or 100 million rows, it takes a bit longer to process the data. If you do it in the Redshift ETL tool, using your own code, it's much faster."
"The ETL way of storing is not up to mark. You have to rely on the naming convention that you're using in Domo because there are no folder systems where you can collate all your workflows and put them into separate folders. A folder system should be there so you can easily identify how you are working. Once you want to make some changes to your ETL, then you can see the whole lineage, identifying what is there and not there."
"There were very few cases on some of the tables, the data tables, where I wish there was an additional feature or two."
"I would like to publish a dashboard for the employees so that they can also see the performance of our organization. But that is not a feature in Domo, although it's something that Zoho provided."
"There is not a data quality or MDM solution in the Pentaho DI suite."
"The reporting definitely needs improvement. There are a lot of general, basic features that it doesn't have. A simple feature you would expect a reporting tool to have is the ability to search the repository for a report. It doesn't even have that capability. That's been a feature that we've been asking for since the beginning and it hasn't been implemented yet."
"I have been facing some difficulties when working with large datasets. It seems that when there is a large amount of data, I experience memory errors."
"I work with the Community Edition, therefore I do not have support. There was an issue that I could not resolve with community support."
"It's not very stable, at least not in the case of the community edition. I'm working with the community edition right now and I think perhaps it is because of that it is not very stable, it causes the system to sometimes hang. I'm not sure if this is the case for pair tiers."
"I'm still in the very recent stage concerning Pentaho Data Integration, but it can't really handle what I describe as "extreme data processing" i.e. when there is a huge amount of data to process. That is one area where Pentaho is still lacking."
"I work with different databases. I would like to work with more connectors to new databases, e.g., DynamoDB and MariaDB, and new cloud solutions, e.g., AWS, Azure, and GCP. If they had these connectors, that would be great. They could improve by building new connectors. If you have native connections to different databases, then you can make instructions more efficient and in a more natural way. You don't have to write any scripts to use that connector."
"As far as I remember, not all connectors worked very well. They can add more connectors and more drivers to the process to integrate with more flows."
More Pentaho Data Integration and Analytics Pricing and Cost Advice →
Domo is ranked 23rd in Data Integration with 35 reviews while Pentaho Data Integration and Analytics is ranked 15th in Data Integration with 48 reviews. Domo is rated 7.8, while Pentaho Data Integration and Analytics is rated 8.0. The top reviewer of Domo writes "Robust, powerful, and easy to use". On the other hand, the top reviewer of Pentaho Data Integration and Analytics writes "It's flexible and can do almost anything I want it to do". Domo is most compared with Tableau, Microsoft Power BI, Databricks, Looker and Amazon QuickSight, whereas Pentaho Data Integration and Analytics is most compared with SSIS, Azure Data Factory, Talend Open Studio, Oracle Data Integrator (ODI) and AWS Glue. See our Domo vs. Pentaho Data Integration and Analytics report.
See our list of best Data Integration vendors.
We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
