Item: Matillion
Rating: 8
Author: Verified User

Use Cases and Deployment Scope

Matillion was used in order to create a Redshift Data warehouse solution. Where the Data warehouse followed the Inmon module and on top of that is a Data mart with multiple aggregations.
It was the product of choice for BI needing to move from an old ETL tool and DB.

Pros and Cons

Ease of use.
Multiple source feeds.
Very good integration with Redshift.
Provides a lot of flexibility with Python scripting.

Target should always be Redshift or it gets complicated.
Python scripts not in Jython don't comply with commit/rollback blocks.
Excel input component is too slow and you are better off processing it in Python.

Return on Investment

The pricing increased dramatically by 30% with short notice. This obviously hurt the OPEX.

Usability

It is easy to use and provides a lot of connections, components and ability to adjust things such as API profiles.

Time to Value

To migrate an existing ETL solution from an old product to Matillion, will require a compete rework with some redesign.
Estimate depends on the complexity required. Would estimate anywhere between 3-9 months.

Scalability

The EC2 instance size determines the licensing costs and in our case we found it to be stable but not overall scalable.

Likelihood to Recommend

It is well suited for anyone needing to create a BI (ETL/ELT) solution on Redshift.
It is very easy to use and provides a lot of components similar to other ETL tools.
Please note all processing is pushed down to the DB (think ELT).
The only downside is some of the under the hood logic is sometimes not acting in the documented/desired fashion, requiring workarounds.

Easy to use and recommended for existing ETL developers

Overall Satisfaction with Matillion