Matillion vs Talend Data Integration

I always suggest Matillion for organizations that do not want to spend money and time developing their own ETL tool, Matillion is a mature one and meet all requirements about it. It is important to check if you have any edge case and have a look if it is covered by Matillion or not.

The same way you design data integration job can be used to design services. It is easy to enhance by custom components and can adapt to all requirements. Talend Data Integration connects to [a] multitude of data sources and streaming service. Very easy interface to design complex applications without spending much time on coding. Easy to learn and master. Talend constantly strives to better itself by adding more features and functionalities.

• Extremely user-friendly workflow orchestration between multiple languages such as SQL, Python, bash, and various API connectors
• Salesforce connectors to pull and push data between systems save us a ton of time
• Matillion Exchange workflows allow for easy sharing of templated best practice transformation jobs with ease
• Very responsive support

• The speed of migration is very good for a Free ETL tool.
• The amount of components or connectors we have is impressive.

• Passing variables between jobs (orchestration or transformation) feels a bit clunky. It can also be frustrating that you can't pass a variable back up to the calling orchestration job, you can only pass it down to child jobs.
• It would be great to have some kind of debug mode, through which you're able to 'step through' the various tasks in an orchestration/transformation job.
• Matillion's generic API functionality is difficult to understand. Things like handling pagination and rate limiting are complex. Although I understand improvements have been made in recent versions.

• Syncing with Git should be made easier
• Can face issues with certain big data spaces
• Support find it difficult to resolve complex issues

With the current experience of Matillion, we are likely to renew with the current feature option but will also look for improvement in various areas including scalability and dependability. 1. Connectors: It offers various connectors option but isn't full proof which we will be looking forward as we grow. 2. Scalability: As usage increase, we want Matillion system to be more stable.

Pretty good UI, especially for a completely web-based system. Source control integration is a bit clunky at times, but overall makes code versioning and branching much more simple, since it's largely within the same context as the rest of the code. Finding some core settings can be difficult - they're just not where one would expect them to be.

We use Talend Data Integration day in and day out. It is the best and easiest tool to jump on to and use. We can build a basic integration super-fast. We could build basic integrations as fast as within the hour. It is also easy to build transformations and use Java to perform some operations.

Overall, I've found Matillion to be responsive and considerate. I feel like they value us as a customer even when I know they have customers who spend more on the product than we do. That speaks to a motive higher than money. They want to make a good product and a good experience for their customers. If I have any complaint, it's that support sometimes feels community-oriented. It isn't always immediately clear to me that my support requests are going to a support engineer and not to the community at large. Usually, though, after a bit of conversation, it's clear that Matillion is watching and responding. And responses are generally quick in coming.

Good support, specially when it relates to PROD environment. The support team has access to the product development team. Things are internally escalated to development team if there is a bug encountered. This helps the customer to get quick fix or patch designed for problem exceptions. I have also seen support showing their willingness to help develop custom connector for a newly available cloud based big data solution

Not really a part of the implementation to give fare insight.

We used Airflow for a year before switching to Matillion. We switched to Matillion because the Airflow servers were not stable, and we didn't have any in-house expertise that could manage the Linux OS which Airflow is built on. We were constantly frustrated by the fact that we had to wait for a consultant whenever we wanted to manage one of the servers, or if something was down we had to wait for someone to fix it. Also, Airflow doesn't have a GUI that is drag and drop. It is a lot more work to manage the flow of the scripts in Airflow, and requires a lot more explanation, especially for an entry level data engineer. There is a lot more coding in Airflow, which is fine if you are a good coder. However, Matillion offers a bigger tool set for those who just want to focus on building an ETL pipeline, and don't care to do a lot of coding.

Talend is much versatile in assimilating various different business use cases. It covers more functionality and is packed with tons of features to explore. It has the ability to fine tune to each project, and not be a one-fits all solution. Problems with Excel, is that it is not suited for large projects, collaboration work. Alteryx is a very costly alternative.

The product scales great for small to medium size teams or groups. For groups larger it becomes more challenging and requires more individual instances depending on the volume of running jobs and concurrent users - it handles 10's of concurrent users and jobs very well but much larger than that would be extremely difficult on the largest instance or cluster that is available at this time.

• Matillion had had a positive impact on our ability to scale up our ETL process without increasing our headcount. We've been able to double the number of jobs we have in the last year.
• A positive impact on the amount of time we need to investigate failures. Coming from other tools that had high rates of failures (say 2 jobs failing a week), we have not seen as many technical failures from Matillion. This reduces the number of resources we focus on tracking down failures, fixing, and re-running jobs by 25%.

• Easy to build complex data transformations.
• Licensing model isn't that flexible.
• Memory mangement for huge volumes of information. You have to modify ETL designs to handle it properly.