It is easy to learn and has good technical support
Bringing data from different sources onto our Snowflake data warehouse.
How has it helped my organization?
* It has helped us avoid a lot of red tape due to compliance.
* It has helped us to get onto the cloud quickly.
What is most valuable?
* It is pretty easy to learn.
* No scripting is required.
* Being cloud native.
What needs improvement?
It is not an end-to-end platform for ETL. It brings in the data. To complete the pipeline, they might want to include some connectors which would put the data into different platforms. This would be helpful.
We are working with different platforms. Most of the connectors that we are looking for are included, but sometimes scripting is required. The good thing is we can reach out to support and have them create the custom connector for us. This can probably be improved.
For how long have I used the solution?
Less than one year.
What do I think about the stability of the solution?
We do not put much stress on it. We run it as a batch right now and spin it up on demand. So, we run it for three hours, then we shut it down. It is not real-time, and there is not a lot of streaming as of now, but it is running in the batch.
What do I think about the scalability of the solution?
The size of our environment is not big. We started six months back. Right now, we only use one node, which is moving the data onto our data warehouse in Snowflake. This node is also very small at this time.
Eventually, we will grow big and quickly, because we just had our three drugs approved. Therefore, a lot of data is going to come over. We will be moving this over to our data warehouse, which will need to increase significantly.
How is customer service and technical support?
The technical support treats us well. They already have a support portal, and they are responsive, which helps.
Which solutions did we use previously?
We haven't used any of the on-premise solutions. What we used before was SQL Server Integration Service (SSIS), and when we were moving to the cloud, we wanted to use something that was cloud native (AWS).
How was the initial setup?
The integration and configuration of this product in our AWS environment was excellent.
We are integrating it with SQL Server and the data coming in is from the on-premise file server. That's what we are connect with right now. Eventually, we will be pulling the data from Google Cloud and Twitter.
What was our ROI?
We are still in the process of moving the data over, so there are no data points as of now.
What's my experience with pricing, setup cost, and licensing?
You probably don't even need to reach out to the company sometimes to purchase it. You can go to the AWS Marketplace. It's very easy to spin up, and the configuration is also easy. It spins up in your own AWS account. The only way you can get the product now is via the AWS Marketplace.
Their pricing is simple. They charge you by the hour. Whatever EC2 instance time that you have been running it for, that's what it's going to charge you for. The licensing is not based off of the per user or per server. They are going by the type of instance you spin up and how long you've been running it, so easy peasy.
Which other solutions did I evaluate?
The other products that we considered were SSIS and Informatica.
We chose Matillion because of the flexibility of the data and the company does not store data on its platform. As a life sciences company, which is HIPAA compliant, we didn't want to move the data over to the platform, so that's why we selected Matillion. It also has additional components that we did not have to pay for, as those features are included with the data. We can scale horizontally with it.
What other advice do I have?
Give it a shot. See how easy it is to get started with the product, because the scripting which is required is minimal. Anybody who is familiar with the SQL Server platform and with SQL scripting can easily pick it up and run with it,
There are no comments to display