Astro by Astronomer vs. Matillion

Astronomer is well suited for workflow and dependency management for enterprise-level data lakes. It is not a product for data processing though. Different source systems can be integrated, it also provides powerful interfaces for alerting and monitoring. Easy to build DAGs, graphical UI, API support makes the product more user-friendly as well. Astronomer also does a great job on user training.

Incentivized

When my team receives a request to import data in from a new place, it's great to have a tool where you can set up those imports in minutes, yet have the capabilities to create customized and complex orchestration as time allows. Because it's easy to send SFTP exports, my internal customers are sometimes surprised that it's not as easy to perform other exports such as e-mailed files or API integrations. If Matillion had output components as varied and excellent as the import components, it would be the perfect solution for so many things we do.

Incentivized

• Workflow management
• Wide availability of plugins
• Dependency management on upstream

Incentivized

• Matillion has a rich transformation library. It provides multiple functionalities, such as join, group by, pivot, various sources, and sinks.
• It provides the security capability as well. All the credentials can be securely stored in Matillion.
• Reusable templates can be built which reduces the redundancy.
• Time to production is very minimal.

Incentivized

• More language agnostic
• Flexible fork and join capabilities
• Near real time UI updates in case of deployment of enhanced DAGs

Incentivized

• Static and monolithic, it will show its limits when running multiple concurrent jobs.
• Github and versioning implementation is messy and broken. Don't use it.
• There's not way to see/query the system resources, just wait for a server to crash due to out of memory. An admin panel would be appreciated + some env variables with updated info.
• API implementation is cumbersome and limited.
• There's no concept of hub and worker engine, everything happens of the same server (designing workflows and executing them). Having separate light ETL engines to run job could be better. (sort of docker/kubernetes/lambda functions).
• Handling of variables is limited especially for returned values from sub components.
• Some components could return more metadata at the end of their execution instead of the standard one.
• Billing is badly designed not taking into account that the server is hosted by the client. Expensive.
• We had several issue with migration where starting a new instance was required and then migrating the content. It was painful and time consuming also have to deal with support and engineering team on Matillion side.
• CDC doesn't work as expected or it is not a mature product yet.

Incentivized

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.

Incentivized

We are able to bring on new resources and teach them how to use Matillion without having to invest a significant amount of time. We prefer looking for resources with any type of ETL skill-set and feel that they can learn Matillion without problem. In addition, the prebuilt objects cover more than 95% of our use cases and we do not have to build much from scratch.

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.

Incentivized

We were able to control on access and built various enviroment for implementation

Incentivized

Astronomer is a fast, secure, scalable workload management solution. It provides world-class user training along with easy to interact support.

Incentivized

Fivetran offers a managed service and pre-configured schemas/models for data loading, which means much less administrative work for initial setup and ongoing maintenance. But it comes at a much higher price tag. So, knowing where your sweet spot is in the build vs. buy spectrum is essential to deciding which tool fits better. For the transformation part, dbt is purely (SQL-) code-based. So, it is mainly whether your developers prefer a GUI or code-based approach.

Incentivized

We're using Matillion on EC2 instances, and we have about 20 projects for our clients in the same instance. Sometimes, we're struggling to manage schedules for all projects because thread management is not visible, and we can't see the process at the instance level.

Incentivized

• It helps to build scalable, available and low maintenance workloads
• Integrated Alerts and notifications helps to detect load issues in the early stages
• Ensures meeting data SLAs

Incentivized

• Matillion has been the backbone of my company's analytical functionalities for 10+ years, so it has a good ROI.
• The price is ok for what our company built with it, but it starts to be less competitive if the tool is not used at its fullest.

Incentivized