We performed a comparison between Matillion ETL and Pentaho Data Integration and Analytics based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It takes less than five minutes to set up and delivers results. It is much quicker than traditional ETL technologies."
"It's highly scalable. It takes upon itself the Redshift scalability, so it's very good."
"We allow non-technical people to use Matillion to load data into our data warehouse for reporting. Thus, it is easy enough to use that we don't always have to get a technical person involved in setting up a data movement (ETL)."
"The loading of data is the most valuable feature of Matillion ETL."
"The product's initial setup phase was easy."
"The technical support treats us well. They already have a support portal, and they are responsive, which helps."
"Matillion ETL is one hundred percent stable."
"The most valuable feature of Matillion ETL is its ease of use. If you have had some experience with other solutions, such as Snowflake, the use of this solution will be simple."
"Sometimes, it took a whole team about two weeks to get all the data to prepare and present it. After the optimization of the data, it took about one to two hours to do the whole process. Therefore, it has helped a lot when you talk about money, because it doesn't take a whole team to do it, just one person to do one project at a time and run it when you want to run it. So, it has helped a lot on that side."
"The abstraction is quite good."
"It has improved our data integration capabilities."
"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."
"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."
"The graphical nature of the development interface is most useful because we've got people with quite mixed skills in the team. We've got some very junior, apprentice-level people, and we've got support analysts who don't have an IT background. It allows us to have quite complicated data flows and embed logic in them. Rather than having to troll through lines and lines of code and try and work out what it's doing, you get a visual representation, which makes it quite easy for people with mixed skills to support and maintain the product. That's one side of it."
"It makes it pretty simple to do some fairly complicated things. Both I and some of our other BI developers have made stabs at using, for example, SQL Server Integration Services, and we found them a little bit frustrating compared to Data Integration. So, its ease of use is right up there."
"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."
"Unlike Snowflake which automatically takes care of upgrading to the latest version and includes additional features, with Matillion ETL we need to do this ourselves."
"It can have multi-environment support. We should be able to deploy it in different environments. Its integration with SAP connection is not so nice, which should be improved. It can also support an on-prem database."
"There are certain functions that are available in other ETL tools which are still not present in Matillion ETL. It would be good to have more features."
"Sometimes, we have issues with the solution's stability and need to restart it for three weeks or more."
"While the UI is good, it could be improved in its efficiency and made easier to use."
"Ideally, I would like it to integrate with Secrets Manager as well as the AWS."
"One of the features that's in development is data privacy in the cloud, along with further SAP integration. For connectivity to SAP systems."
"In the next release, we would like to have connections to more databases."
"Its basic functionality doesn't need a whole lot of change. There could be some improvement in the consistency of the behavior of different transformation steps. The software did start as open-source and a lot of the fundamental, everyday transformation steps that you use when building ETL jobs were developed by different people. It is not a seamless paradigm. A table input step has a different way of thinking than a data merge step."
"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."
"Lumada could have more native connectors with other vendors, such as Google BigQuery, Microsoft OneDrive, Jira systems, and Facebook or Instagram. We would like to gather data from modern platforms using Lumada, which is a better approach. As a comparison, if you open Power BI to retrieve data, then you can get data from many vendors with cloud-native connectors, such as Azure, AWS, Google BigQuery, and Athena Redshift. Lumada should have more native connectors to help us and facilitate our job in gathering information from these new modern infrastructures and tools."
"The web interface is rusty, and the biggest problem with Pentaho is debugging and troubleshooting. It isn't easy to build the pipeline incrementally. At least in our case, it's hard to find a way to execute step by step in the debugging mode."
"I could not connect to our Hadoop environment in an easy and flexible way, and it was important to scale our data warehouse."
"Since Hitachi took over, I don't feel that the documentation is as good within the solution. It used to have very good help built right in."
"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."
"I would like to see improvements made for real-time data processing."
More Pentaho Data Integration and Analytics Pricing and Cost Advice →
Matillion ETL is ranked 4th in Cloud Data Integration with 24 reviews while Pentaho Data Integration and Analytics is ranked 16th in Data Integration with 48 reviews. Matillion ETL is rated 8.6, while Pentaho Data Integration and Analytics is rated 8.0. The top reviewer of Matillion ETL writes "Efficient data integration and transformation with seamless cloud-native integration". 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". Matillion ETL is most compared with Snowflake, Azure Data Factory, AWS Glue, Informatica PowerCenter and SSIS, whereas Pentaho Data Integration and Analytics is most compared with Azure Data Factory, SSIS, Talend Open Studio, Oracle Data Integrator (ODI) and AWS Glue. See our Matillion ETL vs. Pentaho Data Integration and Analytics report.
See our list of best Cloud Data Integration vendors.
We monitor all Cloud 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.
