Matillion

I use it on a daily basis when we process incoming client data of different types. It can be used to build extremely complex workflows to handle data. The automation done on the platform rarely broke and was really stable even during peak data transfer intervals.

The changes made to the workflows on the platform are saved automatically which can be tricky if you make a change by mistake. So whenever you click a wrong button or value, it will be saved unless you undo the changes made and when working with huge complex workflows it can be really time-consuming to find the source of the issue.

I've been using Matillion for about 2 and a half years. I've seen the software improve so much in that time. If I ever found a feature to be lacking, it would be included within the next couple release cycles. The software really seems to adapt as user needs have been evolving. Some of my favorite recent features are the ability to configure some components with just text (really saves me time) and the many Grid orchestration components which allow me to greatly reduce the complexity of the orchestration jobs.

UX is sometimes lacking or inconsistent. For example, let's say my goal is to replace an existing job with a new job of the same name. I delete the old job, and import the new one with the same name. All Orchestration components that used that job will understand to use the new job, but for some reason the scheduler doesn't.
Also, jobs will have validation errors simply because the components haven't been validated (grey borders). It can be confusing because you may be searching for an error in your work when all you actually have to do is revalidate the job.

1) Easy to use
2) Several ingestion integrations
3) Custom RDBMS ingestion support
4) Robust transformation and Orchestration components

No availability of change data capture feature for many databases