We performed a comparison between AWS Glue 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."The solution is highly user-friendly, and its features are easy to use. The new addition of AWS Glue Data Catalog is also very beneficial, making the tool even more helpful for its users."
"AWS Glue is a good solution for developers, they have the ability to write code in different languages and other software."
"It is AWS-integrated. There is end-to-end integration with the other AWS services. It is also user-friendly."
"The most valuable features currently are glue studio, jobs, and triggers."
"The most valuable feature of AWS Glue is scalability."
"The facility to integrate with S3 and the possibility to use Jupyter Notebook inside the pipeline are the most valuable features."
"I appreciate AWS Glue for its cost-effectiveness."
"The solution is serverless so it allows us to transform data while optimizing the cost and performance of Spark jobs."
"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."
"The messaging part is the most valuable feature."
"It's very flexible and a good platform to use."
"The comprehensiveness and depth of Integration Servers' connectors to packaged apps and custom apps is unlimited. They have a connector for everything. If they don't, you can build it yourself. Or oftentimes, if there is value for other customers as well, you can talk with webMethods about creating a new adapter for you."
"When it comes to the user interface, I'm already really used to it. I cannot say anything against it. For me, it's easy to use."
"It's a visual tool, so our transformations can be quickly implemented without a lot of fuss. The fact that we have an easy way to expose REST services is also very interesting. It offers the possibility to connect over GMS to synchronize message brokers."
"Application integrations are offered out-of-the-box, and that is extremely important to us. This is one of the main use cases that we have for it. It is about 60 to 70 percent of the workload in our application today."
"The solution has a very comprehensive and versatile set of connectors. I've been able to utilize it for multiple, different mechanisms. We do a lot of SaaS and we do have IoT devices and the solution is comprehensive in those areas."
"If there's a cluster-related configuration, we have to make worker notes, which is quite a headache when processing a large amount of data."
"There is a learning curve to this tool."
"We face performance issues when using AWS Glue for data transformation and integration."
"In terms of performance, if they can further optimize the execution time for serverless jobs, it would be a welcome improvement."
"The solution’s stability could be improved."
"The interface for AWS Glue could improve, they do not put a lot of details. You can write the code, in PySpark or in Scala, which is a big advantage, it is only easy to use for a developer. It will be difficult for new users to enter the cloud environment."
"I have encountered challenges with multi-region support."
"The mapping area and the use of the data catalog from Glue could be better."
"Version control is not very easy. The packages and the integration server are on Eclipse IDE, but you can't compare the code from the IDE. For example, if you are working on Java code, doing version control and deployment for a quick comparison between the code isn't easy. Some tools or plug-ins are there, such as CrossVista, and you can also play with an SVN server where you have to place your package, and from there, you can check, but you have to do that as a separate exercise. You can't do it from the IDE or webMethods server. You can't just right-click and upload your service."
"The installation process should be simplified for first time users and be made more user-friendly."
"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."
"webMethods Integration Server needs to add more adapters."
"On the monitoring side of things, the UI for monitoring could be improved. It's a bit cumbersome to work with."
"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."
"The product needs to be improved in a few ways. First, they need to stabilize the components of the whole platform across versions. Also, they should stop replacing old components with brand new ones and, rather, improve by evolution."
"The orchestration is not as good as it should be."
More webMethods Integration Server Pricing and Cost Advice →
AWS Glue is ranked 1st in Cloud Data Integration with 37 reviews while webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews. AWS Glue is rated 7.8, while webMethods Integration Server is rated 8.0. The top reviewer of AWS Glue writes "Provides serverless mechanism, easy data transformation and automated infrastructure management". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". AWS Glue is most compared with AWS Database Migration Service, Informatica PowerCenter, SSIS, Informatica Cloud Data Integration and Talend Open Studio, whereas webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and Boomi AtomSphere Integration. See our AWS Glue 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.
