We just raised a $30M Series A: Read our story

Matillion ETL OverviewUNIXBusinessApplication

Matillion ETL is the #6 ranked solution in our list of top Cloud Data Integration tools. It is most often compared to Informatica PowerCenter: Matillion ETL vs Informatica PowerCenter

What is Matillion ETL?

Matillion ETL for Redshift is a fast, modern, easy-to-use and powerful ETL/ELT tool that makes it simple and productive to load and transform data on Amazon Redshift.  100 x faster than traditional ETL technology, up and running in under 5 minutes and prices from $1.37 per hour, with no commitments or up-front costs.

Matillion ETL is also known as Matillion ETL for Redshift, Matillion ETL for Snowflake, Matillion ETL for BigQuery.

Buyer's Guide

Download the Cloud Data Integration Buyer's Guide including reviews and more. Updated: October 2021

Matillion ETL Customers

Thrive Market, MarketBot, PWC, Axtria, Field Nation, GE, Superdry, Quantcast, Lightbox, EDF Energy, Finn Air, IPRO, Twist, Penn National Gaming Inc

Matillion ETL Video

Archived Matillion ETL Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
it_user987312
Solutions Architect at a financial services firm with 501-1,000 employees
Real User
An inexpensive solution that's very fast and extremely easy to use

Pros and Cons

  • "It's highly scalable. It takes upon itself the Redshift scalability, so it's very good."
  • "Ideally, I would like it to integrate with Secrets Manager as well as the AWS."

What is our primary use case?

We're populating a data warehouse, which is the primary focus, but we are also using it to populate our data lake with unstructured data.

What is most valuable?

It's very intuitive and it's super fast once the data's in the cloud. It's simple and visual, as well. I was self-taught. It's so intuitive and easy to use you can actually just teach yourself how to use it. They also have very good support with their YouTube tutorials. Those show you how to do various things if you need help figuring out aspects of the solution.

What needs improvement?

Ideally, I would like it to integrate with Secrets Manager as well as the AWS

For how long have I used the solution?

I've been using the solution for six months.

What do I think about the stability of the solution?

I haven't had any issues with stability.

What do I think about the scalability of the solution?

It's highly scalable. It takes upon itself the Redshift scalability, so it's very good.

We'll be accommodating more data sources going forward. Up until now, it's been a pilot, but we've basically got about another 22 data sources to bring on board. This has been a very successful proof of concept and we will definitely continue using the Matillion going forward.

How are customer service and technical support?

Technical support has been very helpful. They've got quite an efficient help desk and they've always come back to me with good technical answers within 24 hours, which is very acceptable.

Which solution did I use previously and why did I switch?

We had previously used a homegrown ETL system and used a combination of IBM Cognos and ClickView as the presentation layout. They both had their own ETL steps inside them. What we're doing now is we're taking all of the data and moving it into one central data lake warehouse, which is sitting in Redshift, and controlling all the ETL in one place, as well. We're looking to switch off the legacy products now.

Essentially, I want all my data sitting in AWS and I wanted one product that could handle everything, that also needed to be lightweight. I didn't want to go with one of these big Informatica's or other similar tools that are out there, which are all licensed based and very expensive. I wanted something lightweight that was easy to use and relatively cheap.

How was the initial setup?

The initial setup is very straightforward. You can set your first job up in literally minutes. We had our first jobs up almost instantly.

For deployment, the latest version that's just come out integrates with Git, so you can do all of your conversions just using the native Redshift code commit, which is the Git repository. You can actually just do it and it's turnkey. It's very easy. You don't need any people, actually. For maintenance, ideally, we would need about a couple of people. 

We have a small team doing all of the data requirements.

What about the implementation team?

We handled the implementation themselves. That's the beauty of the product. We didn't need to get any external help.

What was our ROI?

It probably is a bit early to measure ROI because at the moment we are having to run all of our processes in parallel and a lot of our existing infrastructure has hidden costs. It definitely will be a lot cheaper going forward and we'll be able to show that. Once we're able to switch off all our legacy servers we'll see very clearly that there's an ROI. 

With on-prem servers, there are always hidden costs, but moving to the cloud makes billing and any extra costs very transparent.

What's my experience with pricing, setup cost, and licensing?

The solution is very cheap. You're paying $2.50 an hour and if you set your service up, which you can do, you're not getting charged. Currently, our ETL process is just an overnight process that runs for about an hour. I can start and stop my server just for an hour if I want to and spent $2.50 a day for an ETL solution. There are no additional costs. It plugs into the AWS marketplace. It's very easy to manage that cost. And if you don't want to use it for a while, you just switch off the EC2 instance and you're not getting billed.

Which other solutions did I evaluate?

We did have a look briefly at Informatica, but it was just too industrial and over the top in terms of price.

Also, Matillion was the only tool that was fully integrated into Redshift. The other tools were basically bolt-ons onto the cloud, but they weren't using the full extent of the card processing capabilities. For this tool, Matillion is actually using the full processing capabilities of Redshift, which includes what they call Massively Parallel Processing on all of their nodes. It's actually a cloud-native product. It was built specifically for Redshift and that was the main difference. There are other tools we could have used, but they required separate EC2 instances to be commissioned and they just didn't seem to integrate as well into the cloud space.

What other advice do I have?

We're using the latest enterprise version of the solution with the public cloud deployment model.

They're constantly improving themselves. I'm quite pleased with the pace of the number of changes that are coming out all the time.

It's a great product and I think it's very competitive. I would recommend the solution.

I would rate the solution nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
ITCS user
Hewlett Packard Enterprise Solution Architect at a tech services company with 11-50 employees
Consultant
It can scale up/down Snowflake warehouses

Pros and Cons

  • "It has improved the costs of managing my customer’s data."
  • "It takes less than five minutes to set up and delivers results. It is much quicker than traditional ETL technologies."
  • "It needs integration with more data sources."

What is our primary use case?

  • ETL process
  • Data warehouse

How has it helped my organization?

It has improved the costs of managing my customer’s data.

What is most valuable?

  • Analytics
  • Integration with SAP and AWS.

What needs improvement?

It needs integration with more data sources. I would also like a better UI because it is complicated to manage it.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

It makes loading and transforming data on Snowflake very fast, easy, and affordable. It is also stable.

What do I think about the scalability of the solution?

It can scale up/down Snowflake warehouses. My client’s size is a mid-sized environment.

How was the initial setup?

It takes less than five minutes to set up and delivers results. It is much quicker than traditional ETL technologies. It loads data into Snowflake from dozens of sources, including S3 and RDS, multiple databases, and APIs.

What's my experience with pricing, setup cost, and licensing?

Purchasing this solution through the AWS Marketplace was quick and easy. 

It was procured through the AWS Marketplace because it keeps things simple. They offer retail-like checkout and bill through your existing Amazon Web Services account.

The AWS pricing and licensing are a cost-effective solution for data integration needs.

What other advice do I have?

It is perfect for when you need your data to never leave your environment using a robust tool. It also ensures the best security practices are deployed within your AWS account.

I have also integrated this solution with Microsoft Azure, but the best performance is with AWS.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Find out what your peers are saying about Matillion, Informatica, SnapLogic and others in Cloud Data Integration. Updated: October 2021.
542,721 professionals have used our research since 2012.
it_user628059
Senior Engineer, Big Data/Data-Warehousing at a manufacturing company with 501-1,000 employees
Vendor
Some of the valuable features are mid-pipeline data sampling and automatic database-object verification.

How has it helped my organization?

  • It enabled an enterprise data-warehouse to be set up and operated, quickly and cheaply.
  • The pipeline UI provides a means to present solutions to analysts and non-tech management for review and agreement.

What is most valuable?

  • It works well with AWS Redshift: I have used Informatica, SnapLogic, and Talend and they do not work well with Redshift.
  • Mid-pipeline data sampling: Without changes to pipelines, one can quickly and easily track down errors.
  • Automatic database-object verification: A fundamental part of how Matillion works is ensuring objects, tables, columns, views, and other metadata are ready and available for use if, and when, a pipeline is started.
  • Run-time parameters: These enable pipelines to be organized and modularized with minimum effort.
  • An array of source-data components: Pulling data from wide tables, such as SFDC, can be setup in seconds. Using Sqoop to pull data to S3, for example, can take hours or even weeks to get right. It is worth noting that Matillion does not cost more if you need more source-data components (SFDC, Marketo, Google AdWords, RDS, MongoDB, etc.).
  • A wide array of in-database DDLs and UDFs accessible from ETL are able to process unstructured data easily, without having to resort to EMR/Hadoop solutions.
  • Integration with other AWS services: It can use Amazon SQS or SNS very easily to extend capabilities, such as doing micro-batch imports (near real-time updates) from source-systems.
  • Python components using Boto and other libraries running on Matillion’s EC2: Matillion can push data from a data warehouse, via REST APIs, to target systems like DynamoDB and Marketo.

What needs improvement?

Compared to the likes of traditional ETLs, like Informatica, SnapLogic, and Talend, or even raw Python scripts, this product needs no improvement, as it is so much better.

Any new product like this has teething problems that get solved pretty quickly in the next release. Better user documentation with more examples would be helpful, especially in areas with run-time parameters or JavaScript inserts.

What do I think about the stability of the solution?

There have been some issues with stability over the first year, but Matillion support is very responsive. I have allowed them to log into our system on occasion.

What do I think about the scalability of the solution?

There are no issues with scalability if one strictly does all transformations in-database, using Redshift’s DDL/SQL.

All the ‘heavy-lifting’ is done by Redshift, as it is MPP. Simply adding more nodes deals with scalability. It is worth noting that Matillion does not cost more if you add more Redshift nodes.

If one uses Python components (as opposed to UDFs), one may encounter scalability issues.

The CPU utilization in WatchTower, of Matillion’s single EC2 (it is not, itself, MPP), will peak. Therefore, it is best to keep a close watch over what your data engineers are doing with Python components.

How are customer service and technical support?

I would give technical support a rating of 5/5.

Which solution did I use previously and why did I switch?

We used Informatica, SnapLogic, and Talend. They do not work well with Redshift and they cost more. They do not understand MPP and much of what they do is outside of Redshift, i.e., not in-database.

You need to put them on a bigger EC2 or buy multiple licenses and have multiple EC2s to manage, in order to get scalability.

How was the initial setup?

The initial setup was very straightforward, as it’s all done from the AWS Marketplace. A wizard steps you through the process of setup. Due to Matillion’s clean and clear architecture, there is not much to configure before one is up and running.

What's my experience with pricing, setup cost, and licensing?

Regardless of the quantity of your data, the size of your cluster, or variety of source systems, the price of Matillion is the same.

The only variable that changes what you pay Matillion is the size of your data engineering team.

  • If your team is just one or two people, then you can just use the [t2.medium @ $1.37/hr]
  • If you have a bigger team, you will need [m4.large @ $2.74/hr] or even [m4.xlarge @ $5.48/hr].

As soon as you can, lock in the yearly discounted price with Matillion, as your level of support availability will increase.

Which other solutions did I evaluate?

We evaluated Informatica, SnapLogic, Talend, Sqoop, and pure Python scripts. Don’t go with any of these if your data can be categorized as any two of the following: volume, variety, and velocity.

What other advice do I have?

  • Experiment and test it ASAP
  • Watch all the videos from Matillion
  • Join their webinar series
  • Talk with existing users

Remember, what Matillion does is simply orchestrate the required jobs. It stands back and lets Redshift do what it is good at.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
ID
Senior Infrastructure Engineer at a tech services company with 51-200 employees
Real User
It is able data sync reliably and ensures that we are compliant with our legal requirements

Pros and Cons

  • "It is pretty user-friendly, even for people who aren't super technical."
  • "It has good integrations with Amazon Redshift and other AWS services."
  • "Going forward, I would like them to add custom jobs, since we still have to run these outside of Matillion."

What is our primary use case?

We use it to migrate data from in-house databases and other data sources into Amazon Redshift.

How has it helped my organization?

  • It is able data sync reliably.
  • It ensures that we are compliant with our legal requirements.

What is most valuable?

  • It is pretty user-friendly, even for people who aren't super technical.
  • It has good integrations with Amazon Redshift and other AWS services.

What needs improvement?

  • It could have better integrations with other databases and other services.
  • I would like to have more customization available.
  • Going forward, I would like them to add custom jobs, since we still have to run these outside of Matillion.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

It is very stable. We have not had to deal with many issues. 

It is running at almost 100% CPU for most of the night. So, it is fairly stressed.

What do I think about the scalability of the solution?

It scales okay. It takes up a good amount of computing resources while it is running, but we wouldn't have too much trouble giving it a little more if it needed it. We have a lot of data, therefore it is hard for me to guess how much we send through it.

How is customer service and technical support?

I haven't personally dealt with the support.

How was the initial setup?

The integrations with a lot of the AWS tools, services, and databases are very convenient. 

It works with DynamoDB, Redshift, Salesforce, and Aurora databases. It has good integrations with all of these.

What's my experience with pricing, setup cost, and licensing?

Purchasing it through the AWS Marketplace is pretty convenient. There is a little bit of back and forth in terms of the licensing based on the machine size, but it seems to have worked out well. it is convenient to have it all as part of our AWS billing.

It is not necessarily a cheap solution. However, it's reasonable priced, especially with the smaller machines that we run it on.

Which other solutions did I evaluate?

We also evaluated Xplenty. 

We chose Xplenty because we wanted to able to have the data live in our VPC, through our network, and not exit our network. Also, the cost was good.

What other advice do I have?

It does the things that it does fairly well, but it would be nice to have some more features, like custom jobs.

Try different tools as much as you can. Make sure the different data that you are trying to sync fits in with the integration the tool provides (or at least most of them). Otherwise, you are going to be paying a lot for not using most of its features.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
MA
Lead Software Engineer at a tech vendor with 10,001+ employees
Real User
The product is easy enough to use that we don't always have to get a technical person involved

What is our primary use case?

Our primary use case is ETL.

How has it helped my organization?

We allow non-technical people to use Matillion to load data into our data warehouse for reporting. Thus, it is easy enough to use that we don't always have to get a technical person involved in setting up a data movement (ETL).

What is most valuable?

Its ease of use.

What needs improvement?

In the next release, we would like to have connections to more databases.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

It seems very stable. We have never had any problems.

What do I think about the scalability of the solution?

We have about 4000 employees.

How is customer service and technical support?

I have never…

What is our primary use case?

Our primary use case is ETL.

How has it helped my organization?

We allow non-technical people to use Matillion to load data into our data warehouse for reporting. Thus, it is easy enough to use that we don't always have to get a technical person involved in setting up a data movement (ETL).

What is most valuable?

Its ease of use.

What needs improvement?

In the next release, we would like to have connections to more databases.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

It seems very stable. We have never had any problems.

What do I think about the scalability of the solution?

We have about 4000 employees.

How is customer service and technical support?

I have never dealt with the technical support.

How was the initial setup?

The integration and configuration of this product on our AWS environment is very easy to do and flexible.

It integrates extremely well with Amazon Redshift.

What's my experience with pricing, setup cost, and licensing?

It was very easy to purchase through the AWS Marketplace, but it was also expensive.

The prices needs to be lower.

Which other solutions did I evaluate?

We did not consider any other products.

What other advice do I have?

Ask about pricing details.

Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Harpreet Singh
Director of Data Architecture at a healthcare company with 51-200 employees
Real User
It is easy to learn and has good technical support

Pros and Cons

  • "It has helped us to get onto the cloud quickly."
  • "The technical support treats us well. They already have a support portal, and they are responsive, which helps."
  • "To complete the pipeline, they might want to include some connectors which would put the data into different platforms. This would be helpful."

What is our primary use case?

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 are customer service and technical support?

The technical support treats us well. They already have a support portal, and they are responsive, which helps.

Which solution did I use previously and why did I switch?

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,

Overall, it is a really good product.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
NV
Application Developer at John Deere & Company
Real User
It saves a lot of money and our upfront costs are less. Performance can be improved for efficiency, and it can be made faster.

Pros and Cons

  • "It can scale to a great extent. It can handle the load that we are putting on it, which is about 5TBs."
  • "Performance can be improved for efficiency, and it can be made faster."
  • "While the UI is good, it could be improved in its efficiency and made easier to use."

What is our primary use case?

We use it for archiving and storing data.

How has it helped my organization?

"It has made our lives much easier," This is what my teammates who were using the other stuff before have said. Then, they moved it to Snowflake. Now, it is much easier and faster to use than before.

What is most valuable?

It is cost-effective. Based on our use case, it's efficient and cheap. It saves a lot of money and our upfront costs are less.

What needs improvement?

  • Performance can be improved for efficiency, and it can be made faster. 
  • Latency could be reduced. Sometimes, it takes longer to fetch data out of it. There are network issues because we experience a little lag.
  • While the UI is good, it could be improved in its efficiency and made easier to use.
  • It can be used by different consumers. So, I would recommend to the company to promote more, because people don't know much about it. If they promote more, they can sell it. They need more marketing.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

It is pretty stable, but you can't blindly rely on it. On a scale of one to ten, I rate it around an eight.

What do I think about the scalability of the solution?

It can scale to a great extent. It can handle the load that we are putting on it, which is about 5TBs.

How is customer service and technical support?

The technical support was good at troubleshooting. The issue that was sent to them was resolved in a couple of days, so it was resolved quickly. 

How was the initial setup?

The integration and configuration was pretty easy. It was completed in about two months.

What was our ROI?

It saves a lot of time.

What's my experience with pricing, setup cost, and licensing?

I have heard from my manager and other higher ups, "This product is cheaper than other things on the market," and they have done the research.

What other advice do I have?

Anybody can help to configure and train on it, learning how to use it. This will help speed up the process.

We use the AWS version only.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
it_user635448
BI Team Lead (Warehouse) at a tech services company with 1,001-5,000 employees
Real User
One of the valuable features is a way to present the ETL process to non-technical observers.

What is most valuable?

Ease of use and a great way to present the ETL process to non-technical observers.

How has it helped my organization?

It has enabled building a data warehouse within three months from the ground up to support WMS reporting.

What needs improvement?

It would be great to have the ability to move windows around to dock in different locations/external windows.

This would involve an ability to physically pin, or move the windows within Matillion (for Redshift).

I know that they can be resized to some extent – but it would be great to collapse the windows, or move them -- similar to moving a tab from a browser so that it's separate from the main GUI.

For how long have I used the solution?

We have been using this solution for six months.

What do I think about the stability of the solution?

We have not encountered any stability issues.

What do I think about the scalability of the solution?

We have not encountered any scalability issues.

How are customer service and technical support?

Matillion's support is great. They are fast to respond, always helpful, and they have great documentation. This includes articles, training videos, and regular software update building on customer feature requests. I would give the support a rating of 10/10.

Which solution did I use previously and why did I switch?

I am not aware of any previous solution.

How was the initial setup?

The setup was straightforward. The user interface is very intuitive and purchasing from the marketplace was simple.

What's my experience with pricing, setup cost, and licensing?

If you are unsure, just send Matillion a quick email, and they’ll get back in touch to help.

Which other solutions did I evaluate?

We did not evaluate any other options.

What other advice do I have?

Just go ahead and take advantage of the initial free period for evaluation. The on-demand price is also very competitive.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
ITCS user
Senior Engineer, Big-Data/Data-Warehousing at a manufacturing company with 501-1,000 employees
Vendor
With built-in verification and sampling, anywhere along the transformation-pipeline, ETL engineers can check, see and sample the data.

How has it helped my organization?

It is helping to make Makerbot a data-driven company.

What is most valuable?

The most valuable features are the components for SFDC, RDS, Marketo, Facebook, and Google AdWords; built-in verification; and scheduling, restarting & logging.

On a Redshift project, before Matillion was released, two people literally spent over one month using Sqoop to pull very wide data tables from Safesforce.com to Redshift. On a new project using Matillion, it took me 10 minutes to set up and begin importing data from Safesforce.com.

Built-in verification and sampling is a fabulous feature for ETL engineers. Anywhere along the transformation-pipeline, one can check, see and sample the data. This saves days & weeks of effort and leads to a far more agile project.

What needs improvement?

More frequent releases are needed, due to API changes from Google, Marketo, and Facebook. They frequently release upgrades to their API and consequently frequently deprecate the older version when only a few months old. The only way to use the Matillion components for these APIs successfully is for the Matillion release process to step up to the plate and have far more frequent "minor" API releases (as opposed to "major" product releases).

Even having these automated might not be a bad idea. Some customers willing to pay might open up a new revenue stream for "platinum" service, to take the headache out of this very valuable set of marketing components in Matillion.

What do I think about the stability of the solution?

I only encountered stability issues when accidentally performing EC2-intensive Python jobs (i.e., not Redshift-intensive SQL). These can kill the Matillion EC2 instance.

What do I think about the scalability of the solution?

I have not encountered any scalability issues.

How are customer service and technical support?

Customer Service:

Customer service is excellent.

Technical Support:

Technical support is above-and-beyond.

Which solution did I use previously and why did I switch?

SnapLogic and Informatica: too slow; for MPP, they are just glorified and expensive Python schedulers.

Python scripts: high maintenance.

How was the initial setup?

Initial setup was straightforward.

What about the implementation team?

I implemented it myself.

What was our ROI?

We achieved ROI in <1 year.

What's my experience with pricing, setup cost, and licensing?

The first two weeks are free; pay by the hour for smallest instance for next 2-3 months; after that, take out yearly discounted rate from AWS Marketplace for instance/devs in team.

Which other solutions did I evaluate?

We also evaluated SnapLogic, Informatica, Talend, and Hadoop.

What other advice do I have?

The mindset of the traditional ETL tools is to off-load transformation to another server/DB. This totally misses the point of MPP and especially of Redshift. Load the data into Redshift early and then transform it inside Redshift ("ELT" not "ETL"). Matillion orchestrates the loading and transformation "pipelines", then gets out of the way whilst Redshift does what it is good at (i.e. the "grunt work").

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Product Categories
Cloud Data Integration
Buyer's Guide
Download our free Cloud Data Integration Report and find out what your peers are saying about Matillion, Informatica, SnapLogic, and more!