Matillion is a productivity platform for data teams. Matillion's Data Productivity Cloud helps data teams – coders and non-coders alike – to move, transform, and orchestrate data pipelines with the goal of empowering teams to deliver quality data at a speed and scale that matches the business’s data ambitions. The vendor states enterprises including Cisco,
N/A
SnapLogic
Score 7.6 out of 10
N/A
SnapLogic is a cloud integration platform with a self-service capacity supported by over 450 prebuilt modifiable connectors. SnapLogic also offers real-time and batch integration processes for interfacing with external data sources, a drag-and-drop interface, and use of the vendors’ Iris AI.
N/A
Pricing
Matillion
SnapLogic
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Matillion
SnapLogic
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
Billed directly via cloud marketplace on an hourly basis, with annual subscriptions available depending on the customer's cloud data warehouse provider.
Talend has a much steeper learning curve. SnapLogic was too expensive but had the best set of features. We did not try Pentaho but that was next on our list.
Matillion ease of use and feature set along with integration capabilities and built in integrations are definitely a step ahead than the other tools and it provides the ability for us ti integrate with refshift, Snowflake and on premise data sources and hence becomes a …
It is very well suited for ETL on the cloud. Whenever there is something that can be accomplished with no code or little code, Matillion is a good tool. However, if your pipeline requires a lot of customizations, Matillion should be avoided.
Snaplogic is unique from other IPASS tools if you're very sensitive about data security as they have an on-premise option where your data never needs to leave your data center. And data pipelines can be quickly created if Snaplogic has the requisite connector to your data sources. On the downside, if you're transforming a large amount of data for example in training machine learning models, a tool with elastic compute capability is more appropriate.
We leveraged Matillion’s no-code principals to make data manipulation easy for our internal customers. People who don't know how to use SQL no longer need to. Everything in Matillion is self-explained with no or little coding.
We connected Matillion to our data warehouse to allow people to read raw data, transform it, then write results back to their sandbox databases. The drag and drop component design allowed customers to create complex data models at the speed of thought without any risk to production data.
With sharing capabilities between projects enabled, everyone was able to help each other when questions arose which instilled a strong sense of collaboration and community.
I think a non-CLI approach to installing and uninstalling python libraries would be nice. I mean, it isn't difficult to install a python library via Linux or CLI, but I imagine most companies don't feel comfortable allowing Matillion users to go on a virtual server and installing it themselves. Requirement.txt file for installing libraries would be simple, and maybe that could also be used to uninstall libraries as well......or maybe the library gets automatically downloaded if it is imported into a python script but the library doesn't exist.
Python Component is lacking very much in terms of UI. It would be unrealistic for me to suggest Matillion build its own EDI, but it would be nice if a python component could connect to a local IDE. Right now, if you want to write any decent length python code, you are going to be stuck copying and pasting your code from your local IDE.
It is also very difficult to debug in Matillion because you can't set breakpoints. Local IDE integration can resolve that.
I would like to have more templates to copy from for certain simplistic scenarios. For instance, a template for a job that fails which sends an AWS SNS with the Job name, component it failed on, and the error message. It wasn't as simple as I thought it would be to figure out and having to use a shared job for such circumstances can be painful because you have to export a bunch of variables.
There should be a drop down list for Global Matillion variables as it is difficult to remember at times.
With the current experience of Matillion, we are likely to renew with the current feature option but will also look for improvement in various areas including scalability and dependability. 1. Connectors: It offers various connectors option but isn't full proof which we will be looking forward as we grow. 2. Scalability: As usage increase, we want Matillion system to be more stable.
This has been hands down the BEST software company I have ever used and dealt with. I am a 25 year IT veteran at this college. They go above and beyond in soliciting our feedback/input and proactively follow up about bugs, issues, etc. I have given multiple potential clients my thoughts and after seeing the SL demo they all sign up. I appreciate their support model, it's REFRESHING!
It has been easy to train new employees who don't have previous experience with Matillion. It is quite self-explanatory. There are quite a few things that can be done with Python, however, we have not really looked into this feature much but likely will do in the future. Mostly, it is drag and drop of components and environments can be set up so easy to set up connections as well.
Overall, I've found Matillion to be responsive and considerate. I feel like they value us as a customer even when I know they have customers who spend more on the product than we do. That speaks to a motive higher than money. They want to make a good product and a good experience for their customers. If I have any complaint, it's that support sometimes feels community-oriented. It isn't always immediately clear to me that my support requests are going to a support engineer and not to the community at large. Usually, though, after a bit of conversation, it's clear that Matillion is watching and responding. And responses are generally quick in coming.
They can be prompt but they have not been as useful as I've wanted. We had a bug that affected many of our customers through an API connection between SnapLogic and our platform. Eventually they were able to figure it out, but it took a long time of negotiating between our engineering team and theirs. Additionally, we installed the SnapLogic groundplex for our customers and we've run into a bunch of problems of connectivity. If SnapLogic offered to be on those calls with our clients to troubleshoot how to fix these problems, I would give them a better grade here.
Matillion ran circles around Stitch and Striim both in functionality, setup, and performance. There was no real comparison. Fivetran massively outperforms Matillion in pretty much every facet of the production from setup, maintenance, visibility, and usability. It already has the ability to connect any data source to a destination regardless of database type. Why we chose Matillion over Fivetran is that, for our current needs, Matillion provides us with the functionality that we need and a much more competitive price for a smaller company.
We opted for SnapLogic due its ease of use and the flexibility it offers, it was the platform that was strongest in both application integration and data integration and both were use cases we wanted to be able to cover.
I have been able to connect Matillion to AWS Aurora Databases, MySQL databases, Rest APIs, Files in AWS S3, etc. Being able to load all of that disparate data into one datalake has made data mining and reporting a lot simpler. I wish everything could be implemented as easily as Matillion.
