We performed a comparison between Matillion ETL and webMethods Integration Server based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It has helped us to get onto the cloud quickly."
"Matillion ETL has great Git integration that is perfect and convenient to use."
"The loading of data is the most valuable feature of Matillion ETL."
"The product's initial setup phase was easy."
"The most valuable feature of Matillion ETL is the ETL. The solution is open-source which provides advantages, such as good performance and high efficiency. Additionally, it supports three data types which eliminates predefining the data, and we can write script models in Python."
"The most valuable feature of Matillion ETL is the UI experience in which you can drag and drop most of the transformation."
"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."
"It has good integrations with Amazon Redshift and other AWS services."
"Segregation of deployment for the environments is the most valuable feature of the solution."
"It frankly fills the gap between IT and business by having approval and policy enforcement on each state and cycle of the asset from the moment it gets created until it is retired."
"I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well."
"webMethods platform is used to build an EAI platform, enabling communication between many internal systems and third-party operators."
"Best feature is Insight for monitoring, and as a debugging tool. It has saved us a lot of time during crisis situations."
"It is a very stable product."
"One valuable feature is that it is event-driven, so when new data is available on the source it can be quickly processed and displayed. Integration is definitely another useful feature, and B2B is one area where webMethods has its own unique thing going, whereby we can do monitoring of transactions, monitoring of client onboarding, and so on."
"How simple it is to create new solutions."
"Ideally, I would like it to integrate with Secrets Manager as well as the AWS."
"In the next release, we would like to have connections to more databases."
"One of the features that's in development is data privacy in the cloud, along with further SAP integration. For connectivity to SAP systems."
"Going forward, I would like them to add custom jobs, since we still have to run these outside of Matillion."
"It needs integration with more data sources."
"Our main challenge currently is that Matillion runs on an EC2 instance, limiting us to running only two processes simultaneously at the entry level."
"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."
"I would like to have a dashboard where I can see all of the communication between components and the configuration."
"We got the product via a reseller, and the support from the reseller has been less than desirable."
"Large file handling is pretty hard comparatively to other middleware tools."
"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."
"This product has too many gaps. You find them after update installations. This should be covered by automatic testing."
"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."
"t doesn't represent OOP very well, just a method and proprietary interface called IData."
"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."
More webMethods Integration Server Pricing and Cost Advice →
Matillion ETL is ranked 4th in Cloud Data Integration with 24 reviews while webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews. Matillion ETL is rated 8.6, while webMethods Integration Server is rated 8.0. The top reviewer of Matillion ETL writes "Efficient data integration and transformation with seamless cloud-native integration". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". Matillion ETL is most compared with Snowflake, Azure Data Factory, AWS Glue, Informatica PowerCenter and SSIS, whereas webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and Boomi iPaaS. See our Matillion ETL vs. webMethods Integration Server report.
See our list of best Cloud Data Integration vendors.
We monitor all Cloud Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
