My experiences using Matillion
January 10, 2025
My experiences using Matillion
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Matillion
We totally rebuilt our legacy data warehouse software and built a datalake in Matillion using Snowflake as a database. Before that we used Informatica PowerCenter on premise. Although Informatica also offered a cloud solution (IICS) which offered more flexibility, we switched to Matillion because it met all our wishes to set up a metadata-driven data warehouse. Iterating through (meta) data in Matillion is very simple and the results can be used as variables in almost all Matillion components. So if the data definitions of our sources change we only have to change metadata and almost never software anymore. There are also components available that can read metadata from out source systems, so if a column in a table in the source system is added then it also automatically added to our datalake and data warehouse
Pros
- Iterating through data
- Behaviour of components can be completly influenced using variables
- Components are available to solve almost any issue
- Matillion is easy to learn for those who already know other ETL/ELT tools
Cons
- The working of shared components was in our solutions not as we expected, so we don't use them anymore
- API's are hard to configure
- In Informatica PowerCenter we had 8 connections to Snowflake. In Matillion we only had 4. So we expected that the time of our night run would be doubled. But the concurrency in Matillion is so good that almost all night run times were the same or even shorter.
- Because we were able to create a totally data-driven solution implementation of new source reduces development time between 80 and 100% compared to Informatica Powecenter development.
- Because we created this data-driven solution (that automatically adapts to the source system definitions) our night runs almost never fail anymore (e.g. when a column in a source table is removed the job recognizes this, changes the Snowflake table definitions in our datalake or DWH and just continues)
It was all about understanding the philosophy of the tool. I only had some introduction course given by Matillion (a few hours). After that it was easy to start building solutions following our requirements. I think I needed only a few months to completely build our Datalake solution. For our dataware house solution about the same time was used.
In my opinion Matillion provides more flexibility then the other tools I mentioned.
Do you think Matillion delivers good value for the price?
Yes
Are you happy with Matillion's feature set?
Yes
Did Matillion live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Matillion go as expected?
Yes
Would you buy Matillion again?
Yes
Comments
Please log in to join the conversation