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 has helped us to get onto the cloud quickly."
"It is an incredibly user-friendly and intuitive tool, making the learning curve quite smooth"
"The most valuable feature of Matillion ETL is the UI experience in which you can drag and drop most of the transformation."
"The technical support treats us well. They already have a support portal, and they are responsive, which helps."
"It's been able to do everything we require."
"It can scale to a great extent. It can handle the load that we are putting on it, which is about 5TBs."
"Matillion ETL has great Git integration that is perfect and convenient to use."
"It has improved the costs of managing my customer’s data."
"It's my understanding that the product can scale."
"I can use Python, which is open-source, and I can run other scripts, including Linux scripts. It's user-friendly for running any object-based language. That's a very important feature because we live in a world of open-source."
"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."
"Data transformation within Pentaho is a nice feature that they have and that I value."
"We also haven't had to create any custom Java code. Almost everywhere it's SQL, so it's done in the pipeline and the configuration. That means you can offload the work to people who, while they are not less experienced, are less technical when it comes to logic."
"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."
"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."
"This solution allows us to create pipelines using a minimal amount of custom coding."
"To complete the pipeline, they might want to include some connectors which would put the data into different platforms. This would be helpful."
"When using the SQL loader type there were not a lot of pre-processing features for the data. For example, if there is a table with twenty columns, but we only want to load ten columns. In that case, we can use a security script to select the specific columns needed. However, if we want to perform extensive pre-processing of the data, I faced some challenges with Matillion ETL. I did not encounter many challenges, but my overall experience is limited as I only have three years of experience."
"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."
"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."
"Going forward, I would like them to add custom jobs, since we still have to run these outside of Matillion."
"I found some of the more complex aspects of ETL challenging, but I grasped the concepts fairly quickly."
"One of the features that's in development is data privacy in the cloud, along with further SAP integration. For connectivity to SAP systems."
"The current version is a bit more limited because it's on a virtual machine, and everything executes on that one virtual machine."
"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."
"I could not connect to our Hadoop environment in an easy and flexible way, and it was important to scale our data warehouse."
"The performance could be improved. If they could have analytics perform well on large volumes, that would be a big deal for our products."
"I was not happy with the Pentaho Report Designer because of the way it was set up. There was a zone and, under it, another zone, and under that another one, and under that another one. There were a lot of levels and places inside the report, and it was a little bit complicated. You have to search all these different places using a mouse, clicking everywhere... each report is coded in a binary file... You cannot search with a text search tool..."
"I would like to see improvements made for real-time data processing."
"The testing and quality could really improve. Every time that there is a major release, we are very nervous about what is going to get broken. We have had a lot of experience with that, as even the latest one was broken. Some basic things get broken. That doesn't look good for Hitachi at all. If there is one place I would advise them to spend some money and do some effort, it is with the quality. It is not that hard to start putting in some unit tests so basic things don't get broken when they do a new release. That just looks horrible, especially for an organization like Hitachi."
"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."
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.
