I primarily use Matillion Data Productivity Cloud for ingest functions. In one client's case, we switched from typical AWS tools and changed all of the blueprints and architecture to use Matillion Data Productivity Cloud for ingesting information from GCP and reading SQL data.
External reviews
External reviews are not included in the AWS star rating for the product.
Utilize data systems securely and efficiently while connectivity issues require attention
What is our primary use case?
What is most valuable?
Matillion Data Productivity Cloud is effective for ingest functions, particularly when moving information to Snowflake and performing many transformations. Its integration with existing environments, utilizing security measures like VPN and VPCs, makes it a secure choice. However, its features are not notably different from other products in the market.
What needs improvement?
There are problems with GCP connectivity. Specifically, connections to BigQuery for extracting information are complex, and the optimization of the extraction process requires improvements. I raised this issue with Matillion's support, but the solution is pending with their research team.
For how long have I used the solution?
I have been working with Matillion Data Productivity Cloud for two years.
What do I think about the stability of the solution?
Matillion Data Productivity Cloud is stable and functions reliably as a product.
What do I think about the scalability of the solution?
The autoscale process works well, allowing the system to start another node automatically if the first machine reaches 80% capacity. However, the limitation is the number of parallel jobs due to the direct relation to the cores on the machine.
How are customer service and support?
Matillion's technical support is excellent. They communicate effectively and respond quickly to all inquiries.
How would you rate customer service and support?
Neutral
How was the initial setup?
The initial setup is straightforward. We completed the foundations process using Infrastructure as Code (IaC), which standardizes and simplifies the deployment process.
What was our ROI?
In terms of ROI, one client found that using Snowflake tasks was more cost-effective than Matillion's credits cost. Consequently, we adjusted our processes to use Matillion Data Productivity Cloud only for extraction and ingestion, while Snowflake handled all transformations and jobs.
What's my experience with pricing, setup cost, and licensing?
While pricing can be an issue compared to other solutions, Matillion Data Productivity Cloud offers discounts and special deals, especially when dealing with high-volume clients or fewer existing clients in specific regions, like Spain.
Which other solutions did I evaluate?
In many cases, clients consider buying a product from the same hyperscaler for an end-to-end solution, such as Microsoft Fabric.
What other advice do I have?
While Matillion Data Productivity Cloud can be valuable, it is challenging to recommend due to its pricing and limited clientele in regions like Spain. Overall, I would rate Matillion as a six out of ten.
Helps us monitor real-time data, but the scalability needs improvement
How has it helped my organization?
In a project where we migrated from on-prem solutions to the cloud, we used Matillion and Snowflake, which streamlined the process significantly.
What is most valuable?
Matillion ETL's ability to conduct end-to-end data migration is valuable. We can create jobs, monitor them, and manage workflows effectively.
What needs improvement?
The product's scalability needs improvement. Perhaps adding more connectors would be beneficial.
What do I think about the stability of the solution?
The product is quite stable and can handle complex data integration tasks well.
What do I think about the scalability of the solution?
I rate the platform scalability around six or seven. Depending on the specific architecture, parallel processing needs, and data types involved, it could be optimized.
How are customer service and support?
I haven't contacted the technical support team, but the online documentation and community resources are quite sufficient.
How was the initial setup?
A team of two to three ETL architects and data engineers is required to work on deployment.
What other advice do I have?
We can monitor and manage real-time data pipelines, analyze task logs, and automate data pipelines wherever possible. We also apply parameterization to improve efficiency using the product.
It adapts well to changing data volumes and types. I would recommend it, especially for cloud data integration.
I rate it a seven or eight.
Easy to use ELT tool for staging and transforming you data
The new performance monitor is great for checking on jobs across projects and understand how your server is performing.
Consistent updates keep the tool ever improving
There could be better logging, especially when using transaction control and updates are run sequentially instead of in parallel.
Better API access for pulling job history and average run times.
Git integraton is kind of clunky for larger teams
Matillion is easy to use and a helpful ETL scheduler
The scheduler is very handy.
The webhook to send Slack messages for failures is awesome.
We've moved to Github directly, and then use a Python component to read in and execute our ETL scripts stored on Github.
There is a weird redirect every time I sign in that makes me have to load the page twice.
We also have predictive models now running each day through Matillion.
Great for most ETL use cases. A few limiting factors to consider
Helps in the implementation of Snowflake but lineage is weak
What is our primary use case?
The tool's primary use case is implementing Snowflake, including building a data warehouse atop our source systems and facilitating data exchange with customers and suppliers utilizing Snowflake.
What is most valuable?
The tool's middle-dimensional structure significantly simplifies obtaining the right data at the appropriate level. This feature makes deploying our applications easier since we utilize a single source without publishing data from various sources. Consequently, presenting data becomes more straightforward, and customer interactions involve no copying or pasting, streamlining the exchange process.
With Matillion ETL, we read data from different warehouse source systems. We create a unified version of the data in the data warehouse using the ETL functionality. Mapping tables address the challenges of different source systems, ensuring the data is at the correct level of detail. It is very strong and comes with much functionality, including monitoring.
What needs improvement?
The tool's lineage is very weak.
For how long have I used the solution?
I have been using the product for three and a half years.
What do I think about the stability of the solution?
The tool is stable.
How are customer service and support?
I haven't contacted the technical team yet.
What about the implementation team?
Matillion ETL's deployment can be done in-house.
What's my experience with pricing, setup cost, and licensing?
Matillion ETL is expensive.
What other advice do I have?
The tool seems to reduce complexity rather than boost performance. The overall process remains somewhat intricate. I don't think we've observed any performance improvements using my team. I rate the overall product a seven out of ten.
Matillion review as data engineer
2. easy to setup batch jobs
3. provide the support to setup workloads on aws and snowflake
4. git integration enable version control
2. no CICD enabled
3. hard to do unit test
4. data load component we used to ingest fata from sql server into snowflake does not have retry function
2. data teamsformation to join multiple fata sources together for final report
3. data orchestration for batch jobs
Powerful and scalable cloud-native data integration platform
User Friendly Etl Tool for cloud connectivity
When it comes to support it takes a lot of time to to resolve the query through support. Scheduling functionality needs some improvement.