Overall Satisfaction with Matillion
Within the Business Analytics team, Matillion was introduced as a new ELT tool after team extension. In that time, we had four active BI developers and the main need was a centralized project repository that will make the daily workload easier. We are using Matillion for development and maintenance of the data warehouse and integration of more than 20 data sources.
- Tailor-made for Redshift, including most of the features like Spectrum.
- Cloud-based solution with centralized project repository, easy team collaboration.
- Built-in scheduling and monitoring, everything in one place.
- Awesome support, the short time from raising a question to the solution providing.
- Documentation is not always updated in time when new stuff is implemented.
- Some connectors already implemented still have some bugs which make them useless for our use case.
- Small fine tuning still missing, in terms of covering all use cases of some connectors.
- Shorter time to market. Development from a month decreased to two weeks including testing.
- Developers are more focused (>80% of the time) on a specific topic instead of searching for different technical solutions.
After just two months we had complex processes running on a production environment. And now after six months, we became really proficient users of Matillion which are also taking care of optimization improvements and not just a development.
Before the ETL tool we made the decision to stick to Redshift as a database. Compared to listed products (that I used) I would say that the decision was easy if we consider the sync with AWS and Redshift, cloud-based solution, team collaboration, built-in scheduling, and monitoring.
Matillion Feature Ratings
Using Matillion
5 - DWH & BI Engineers
Matillion Support
Pros | Cons |
---|---|
Quick Resolution Problems get solved Kept well informed Immediate help available Support understands my problem Quick Initial Response | Poor followup |
Yes - Yes. Sometimes I found bugs but in some of next releases it was fixed. Also most of them were not listed in release bug fixes section.
And one bug is still open for more than a year. Even though we agreed that they implemented that API wrongly somehow it is not prio for development team and it was communicated like support team can't influence/track progress on development.
And one bug is still open for more than a year. Even though we agreed that they implemented that API wrongly somehow it is not prio for development team and it was communicated like support team can't influence/track progress on development.
Multiple times! Not needed to elaborate in detail but at the beginning when support was really needed, Matillion provided it.
Using Matillion
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | None |
- Concurrency
- Deployment
- Debugging
- Python integration
- Some data-source integrations