Matillion

Matillion is very intuitive.
The GUI is easy to use and fairly easy to learn.
The support team is great and they respond to your questions quickly.
I like how the Matillion team is frequently looking to add new functionality and features. The new keyword search functionality is very helpful.

Matillion works great extracting data from a variety of databases and is very efficient unloading onto S3 or Amazon Redshift. However, when we attempted to use it to unload large datasets to Microsoft SQL Server it was very slow and we experienced performance issues.

I like the bunch of API integrated in Matillion it helps me to directly grab the data from different sources without manually extra and import in my database.

I am using Matillion for Redshift from last more than 2 years. When i setup a project in Matillion with connection to a Redshift cluster, sometimes there is a need to extract the data from other instance of Redshift while running job in Matillion. In that case there is straight forward way of getting the data from other instance of Redshift like you have comments to extract the data from databases like SQL Server, Oracle etc. instead of first i need to run another job by connection second Redshift cluster and extract the records after that run different job to load the extracted records from S3 to main Redshift cluster.

It is very easy to implement features and changes to existing workload. It is very good for creating POCs

It is not scalable and has numerous limitations. Concurrency setting for Matillion limits the possibility of using it for multiple warehouses. It is highly insufficient when executing commands parallel and does not utilise the resources to it's full potential.
The environment limitation is also very problematic when trying to scale.

1) Most of the components are user friendly.
2) Development of ETL orchestrations and transformation consumes less time.
3) Advanced features are available in some of the components makes the complex scenarios achievable.

1) OAuth document does not provide the details of proper permissions and access levels on account_id or client_id which are required for a connector.
2) Differentiation of naming convention of metrics between the console and matillion data model , mapping document of these naming conventions is not available.
3) Connector for Outbrain is not available.
4) Indirect file loading concept is not available , for example if we have five files with same structure , reg ex can not be used to load all files in a single component(s3 load,s3 put or excel)
and need to use the file iterator.
5) Loss of properties when the component configuration is changed from Basic to Advanced features , ideally the component should include all the properties of basic and then additional setting should be provided.