Matillion ETL in Healthcare
Overall Satisfaction with Matillion
We utilize Matillion as our primary ETL tool. Due to the complexity of numerous healthcare data sources, we not only chose Matillion for it security and flexibility, but also for its ease of use. One of the main challenges that we face is the different source systems that we pull data from - both internally and externally. It is necessary for the organization to transform both sets of data simultaneously to ensure that we have a standardized EDW. In addition, we have also built template jobs and projects that we are able to utilize when bringing on new data sources. One of the key features that we routinely utilize is the ability to SFTP data files from an AWS instance to a secure SFTP server. While the native object within Matillion is used a vast majority of the time, we also integrated Python script to accomplish more complex cases. We currently utilize the on-prem server side version of Matillion, however we will be transitioning to the cloud-based version of Matillion. This is a game changer for us as we do not want to manage versioning of our Matillion instance.
Pros
- Connecting to new and different data sources
- Transforming data into the enterprise wide data warehouse
- Scheduling and managing job flows
- Password storage and management
Cons
- Communicating new features
- Integrating code version control more easily
- Deeper online documentation
- We are able to process data much quicker and respond to internal needs without much time investment
- Debugging problems in our ETL process is very easy and we can isolate specific issues with data
- Creating new jobs/projects based on templates is seamless
- Very easy to create different environment - development, test and production
The most difficult challenge that we faced was working with our legal team to ensure that data was protected and that nothing important was exposed. Within a week, we were able to get Matillion setup, installed and functioning in basic mode. Whenever we bring in new data sources, it may be necessary to ask external vendors to whitelist Matillion's public IP address, but that has not prevented us from moving very quickly.
We selected Matillion primarily because of it's ability to connect to numerous data sources and easily create transformation jobs. While Fivetran does a better job managing and examining deltas, it is not easy to use and is very non user friendly. SSIS was not a good fit for our team and required a significant amount of attention and server management that we did not want to invest in.
Do you think Matillion delivers good value for the price?
Yes
Are you happy with Matillion's feature set?
Yes
Did Matillion live up to sales and marketing promises?
Yes
Did implementation of Matillion go as expected?
Yes
Would you buy Matillion again?
Yes

Comments
Please log in to join the conversation