Matillion ETL Implementation Team

Chris Hastie - PeerSpot reviewer
Data Lead at InterWorks

The deployment model for Matillion ETL depends on the customer since we are a consultancy with several customers in different capacities. However, the majority of our customers use the cloud-hosted equivalent and host it in their own cloud environment. We don't have any customers who host it on-premises, although it is possible. Customers typically host it on their platform.

Additionally, we do have access to Matillion's own as-a-service beta, but it is only in a private preview environment. We only use it for general testing and experimentation.

For the deployment process in the current world, you would log in to Resilient and create an account on Matillion Hub. That is the process that allows you to get started with Matillion Hub. Matillion often helps you with this process if you are a Matillion partner. You go through Matillion Hub, put in your details, and then you can decide which platform you want to deploy your virtual machine to. You can choose between Azure, AWS, and GCP.

When you choose a platform, it will give you a template report bespoke to that environment. For example, if you're deploying to AWS, it will give you an ARM template. If you do it on Azure, it will provide you with a kind of shared instance template or a VM template. Then you just need to configure a few options, and it will deploy the instance to stand up for you. That's the current process.

In the new world, when Matillion launches its Data Productivity Cloud, things will change. It's delivered as a service, so I imagine the deployment will be much simpler. But my understanding is that it will still leverage your own custom zone containers to process the workloads. So the process will be very similar to what's currently used to deploy the virtual machines, but it will be used to deploy the elastic containers to which the workload will be pushed out.

View full review »
AntonHaupt - PeerSpot reviewer
Data Architect at Capitec

It seamlessly integrates with CodeConnect, which is the AWS Git repository, but it also supports integration with any Git repository, whether it's GitHub, GitLab, or another platform. Regardless of your choice of change control tool, Matillion can accommodate it. It simplifies the process by converting JSON payloads into a usable format, allowing for easy promotion from one environment to another. There's no maintenance required from our end; it's all handled automatically by the vendor. We receive weekly patches and periodic version updates, ensuring the solution stays up-to-date without any intervention from our side.

View full review »
MG
Director of IT Operations at a financial services firm with 10,001+ employees

Our in-house team did the implementation. We primarily had one person working on it. You can count overheads for security, management approvals, and everything it requires, but the actual work is done by only one person.

View full review »
Buyer's Guide
Matillion ETL
March 2024
Learn what your peers think about Matillion ETL. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
763,955 professionals have used our research since 2012.
SK
Data Engineer

We did the deployment of the solution with some assistance.

View full review »
PT
Data analyst at a tech services company with 51-200 employees

Matillion ETL's deployment can be done in-house. 

View full review »
Buyer's Guide
Matillion ETL
March 2024
Learn what your peers think about Matillion ETL. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
763,955 professionals have used our research since 2012.