We performed a comparison between Azure Data Factory and webMethods Integration Server based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The solution has a good interface and the integration with GitHub is very useful."
"UI is easy to navigate and I can retrieve VTL code without knowing in-depth coding languages."
"Microsoft supported us when we planned to provision Azure Data Factory over a private link. As a result, we received excellent support from Microsoft."
"Its integrability with the rest of the activities on Azure is most valuable."
"The workflow automation features in GitLab, particularly its low code/no code approach, are highly beneficial for accelerating development speed. This feature allows for quick creation of pipelines and offers customization options for integration needs, making it versatile for various use cases. GitLab supports a wide range of connectors, catering to a majority of integration needs. Azure Data Factory's virtual enterprise and monitoring capabilities, the visual interface of GitLab makes it user-friendly and easy to teach, facilitating adoption within teams. While the monitoring capabilities are sufficient out of the box, they may not be as comprehensive as dedicated enterprise monitoring tools. GitLab's monitoring features are manageable for production use, with the option to integrate log analytics or create custom dashboards if needed. The data flow feature in Azure Data Factory within GitLab is valuable for data transformation tasks, especially for those who may not have expertise in writing complex code. It simplifies the process of data manipulation and is particularly useful for individuals unfamiliar with Spark coding. While there could be improvements for more flexibility, overall, the data flow feature effectively accomplishes its purpose within GitLab's ecosystem."
"The solution includes a feature that increases the number of processors used which makes it very powerful and adds to the scalability."
"The user interface is very good. It makes me feel very comfortable when I am using the tool."
"I am one hundred percent happy with the stability."
"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."
"We needed a tool that was able to orchestrate and help us configure our APIs so that we could maintain and see the heartbeat, traffic, trends, etc."
"Most of the work in our organization can be more easily done using the tool."
"The messaging part is the most valuable feature."
"What I found most valuable in webMethods Integration Server is that it's a strong ESB. It also has strong API modules and portals."
"It's obvious that the heart of the product lies here. It's comprised of all aspects of ESB (Enterprise Gateway, Adapter, TN, Java) and BPM (task, rules engine)."
"From a user perspective, the feature which I like the most about Integration Server is its designer."
"One [of the most valuable features] is the webMethods Designer. That helps our developers develop on their own. It's very intuitive for design. It helps our developers to speed the development of services for the integrations."
"It can improve from the perspective of active logging. It can provide active logging information."
"There is always room to improve. There should be good examples of use that, of course, customers aren't always willing to share. It is Catch-22. It would help the user base if everybody had really good examples of deployments that worked, but when you ask people to put out their good deployments, which also includes me, you usually got, "No, I'm not going to do that." They don't have enough good examples. Microsoft probably just needs to pay one of their partners to build 20 or 30 examples of functional Data Factories and then share them as a user base."
"The Microsoft documentation is too complicated."
"The solution needs to be more connectable to its own services."
"Azure Data Factory should be cheaper to move data to a data center abroad for calamities in case of disasters."
"The solution should offer better integration with Azure machine learning. We should be able to embed the cognitive services from Microsoft, for example as a web API. It should allow us to embed Azure machine learning in a more user-friendly way."
"For some of the data, there were some issues with data mapping. Some of the error messages were a little bit foggy. There could be more of a quick start guide or some inline examples. The documentation could be better."
"When working with AWS, we have noticed that the difference between ADF and AWS is that AWS is more customer-focused. They're more responsive compared to any other company. ADF is not as good as AWS, but it should be. If AWS is ten out of ten, ADF is around eight out of ten. I think AWS is easier to understand from the GUI perspective compared to ADF."
"In terms of scale, I would give it a four out of 10."
"It is quite expensive."
"A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs."
"The market webMethods Integration Server falls under is a very crowded market, so for the product to stand out, Software AG would need to get traction in the open source community by releasing a new version or a base version and open source it, so people can create new custom components and add it to the portfolio."
"Large file handling is pretty hard comparatively to other middleware tools."
"The price should be reduced to make it more affordable."
"The Software AG Designer could be more memory-efficient or CPU-efficient so that we can use it with middle-spec hardware."
"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."
More webMethods Integration Server Pricing and Cost Advice →
Azure Data Factory is ranked 1st in Data Integration with 81 reviews while webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews. Azure Data Factory is rated 8.0, while webMethods Integration Server is rated 8.0. The top reviewer of Azure Data Factory writes "The data factory agent is quite good but pricing needs to be more transparent". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". Azure Data Factory is most compared with Informatica PowerCenter, Informatica Cloud Data Integration, Alteryx Designer, Snowflake and Microsoft Azure Synapse Analytics, whereas webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and IBM WebSphere Message Broker. See our Azure Data Factory vs. webMethods Integration Server report.
We monitor all 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.
