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."The technical support treats us well. They already have a support portal, and they are responsive, which helps."
"It's highly scalable. It takes upon itself the Redshift scalability, so it's very good."
"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."
"The product's initial setup phase was easy."
"The most valuable feature of Matillion ETL is its user-friendly graphical interface."
"The most valuable feature of Matillion ETL is the ETL. The solution is open-source which provides advantages, such as good performance and high efficiency. Additionally, it supports three data types which eliminates predefining the data, and we can write script models in Python."
"It takes less than five minutes to set up and delivers results. It is much quicker than traditional ETL technologies."
"It has helped us to get onto the cloud quickly."
"This solution allows us to create pipelines using a minimal amount of custom coding."
"One of the most valuable features is the ability to create many API integrations. I'm always working with advertising agents and using Facebook and Instagram to do campaigns. We use Pentaho to get the results from these campaigns and to create dashboards to analyze the results."
"One of the valuable features is the ability to use PL/SQL statements inside the data transformations and jobs."
"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."
"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."
"It's my understanding that the product can scale."
"I absolutely love Hitachi. I'm one of the forefront supporters of Hitachi for my firm. It's so easy to integrate within our environments. In terms of being able to quickly build ETL jobs, transform, and then automate them, it's really easy to integrate throughout for data analytics."
"Data transformation within Pentaho is a nice feature that they have and that I value."
"I am looking forward to seeing the expansion of the source range for their data loader product."
"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."
"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 product must enhance its near-real-time data capture feature."
"Our main challenge currently is that Matillion runs on an EC2 instance, limiting us to running only two processes simultaneously at the entry level."
"Going forward, I would like them to add custom jobs, since we still have to run these outside of Matillion."
"The improvement area could be possible if the tool provides better integration capabilities with other ecosystems, including governance tools or data cataloging tools, as it is currently an area where the solution is lacking."
"While the UI is good, it could be improved in its efficiency and made easier to use."
"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."
"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 would like to see support for some additional cloud sources. It doesn't support Azure, for example. I was trying to do a PoC with Azure the other day but it seems they don't support it."
"The support for the Enterprise Edition is okay, but what they have done in the last three or four years is move more and more things to that edition. The result is that they are breaking the Community Edition. That's what our impression is."
"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."
"A big problem after deploying something that we do in Lumada is with Git. You get a binary file to do a code review. So, if you need to do a review, you have to take pictures of the screen to show each step. That is the biggest bug if you are using Git."
"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."
"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."
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.
