There's room for improvement in how it handles data streaming capabilities. Our main challenge currently is that Matillion runs on an EC2 instance, limiting us to running only two processes simultaneously at the entry level. This constraint means we can run about sixteen jobs concurrently at the moment. However, once we transition to the SaaS offering, scalability will no longer be an issue. With the SaaS solution, we'll have the flexibility to run as many jobs as needed, making it a natural next step in our progression.

Matillion’s on-premises capabilities don’t allow you to build something customized. I will give an example of tables to explain it. If we want to do a lookup, we have to copy the whole table with three million rows in it, every time. It is not cost-effective for me. We have these three million rows ported over in our S3 bucket. We have to pay for that and Snowflake as well. So, we have told them to build up a custom solution allowing us to bring over the data we care about, using the records and the drivers. But, that wasn’t out-of-the-box. So, the default way to work is to port everything over from on-premises to your AWS environment. For me, it is not cost-effective in the long run.

So the main thing I would like to see improved in Matillion are two things. Firstly, their ability to process concurrent workloads. Right now, the concurrency reaches a stalling point if too many things are added, and it gets stuck waiting for each one to finish. 

Secondly, Matillion needs an improvement in its backend integration and the way that it pushes things through. It is already good, but it could be cleaner. I will say that I think both of those issues are being addressed in the new platforms that are coming out.  Matillion Unlimited Scale is the new answer to concurrent workloads, and Matillion Data Productivity Cloud is their new software-as-a-service version of a Matillion ETL provider, including a deeper git integration. So my concerns are being addressed, but those are the two things that stand out to me the most right now.

Sometimes, we have issues with the solution's stability and need to restart it for three weeks or more. There is some room for improvement in job clusters for Databricks.

The product must enhance its near-real-time data capture feature. Also, if they enhance CDC functionality, we can replace multiple components with one component. Otherwise, we must purchase a different component for CDC functionality and another component for data transformation. This added feature will help the user do everything with a single component.

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.

When using the SQL loader type there were not a lot of pre-processing features for the data. For example, if there is a table with twenty columns, but we only want to load ten columns. In that case, we can use a security script to select the specific columns needed. However, if we want to perform extensive pre-processing of the data, I faced some challenges with Matillion ETL. I did not encounter many challenges, but my overall experience is limited as I only have three years of experience.

The solution could improve by adding support for instructed data types.

When it comes to Snowflake and Matillion ETL, both offer a lot of compatibility and ease of use. The improvement area could be possible if the tool provides better integration capabilities with other ecosystems, including governance tools or data cataloging tools, as it is currently an area where the solution is lacking.

One of the features that's in development is data privacy in the cloud, along with further SAP integration.

For connectivity to SAP systems.

As someone new to the data industry and with limited experience in ETL tools, I'm not familiar with other options. My background was as a university professor until about a year ago, so I'm still getting acquainted with this field. I found some of the more complex aspects of ETL challenging, but I grasped the concepts fairly quickly.

Unlike Snowflake which automatically takes care of upgrading to the latest version and includes additional features, with Matillion ETL we need to do this ourselves. Matillion upgrades the tool quite often, but we need to manually apply it in our environment. This manual process can be done in a few minutes, but it has room for improvement.

Recently, I needed to develop a component that runs queries on Athena, one of the AWS services. Matillion ETL does not have this functionality out of the box, so having an additional component to handle this would be quite convenient. The tool is quite flexible, and there is no source that cannot be easily integrated. The developers are constantly adding new functionality from release to release, responding to market needs. The only thing I was missing at some point was a component for Athena queries.

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.

• 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.

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.

I am looking forward to seeing the expansion of the source range for their data loader product. However, I think they have done a very good job of incorporating a lot of different data sources.

The cost of the solution is high and could be reduced.

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

The tool's lineage is very weak. 

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.

• 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.

There are certain functions that are available in other ETL tools which are still not present in Matillion ETL. It would be good to have more features.

It can have multi-environment support. We should be able to deploy it in different environments. 

Its integration with SAP connection is not so nice, which should be improved. It can also support an on-prem database.

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

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