Try our new research platform with insights from 80,000+ expert users

Microsoft Azure Logic Apps vs webMethods.io comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Microsoft Azure Logic Apps
Ranking in Integration Platform as a Service (iPaaS)
1st
Average Rating
8.0
Reviews Sentiment
8.3
Number of Reviews
38
Ranking in other categories
No ranking in other categories
webMethods.io
Ranking in Integration Platform as a Service (iPaaS)
5th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
91
Ranking in other categories
Business-to-Business Middleware (4th), Enterprise Service Bus (ESB) (3rd), Managed File Transfer (MFT) (10th), API Management (9th), Cloud Data Integration (8th)
 

Mindshare comparison

As of January 2025, in the Integration Platform as a Service (iPaaS) category, the mindshare of Microsoft Azure Logic Apps is 15.9%, up from 13.5% compared to the previous year. The mindshare of webMethods.io is 9.7%, up from 8.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Integration Platform as a Service (iPaaS)
 

Featured Reviews

Ritu-Raj - PeerSpot reviewer
Influenced cost savings by approximately seventy to eighty percent
I have worked on multiple platforms in this space, like MuleSoft, Oracle, Intel, Microsoft, and Dell Boomi. However, Azure Logic Apps is the easiest and most transparent in terms of its operations, licensing cost, and scaling. Being in Azure, the use of the Azure ecosystem becomes quite native with Logic Apps.
Michele Illiano - PeerSpot reviewer
Can function as an ESB along with the core product, with decent integration of message protocols
I have noticed that webMethods ActiveTransfer has had problems when handling large files. For example, when we receive (and perform operations on) files that are larger than about 16 MB, the software starts losing performance. This is why, for most customers who have to deal with big files, I suggest that they use a product other than ActiveTransfer. I would like to note that this problem mainly concerns large files that undergo extra operations, such assigning, unassigning, or file translation. When these operations take place on large files, ActiveTransfer will use up a lot of resources. Within the product itself, I also believe that there is room for improvement in terms of optimization when it comes to general performance. I suspect that the issues underlying poor optimization are because it is all developed in Java. That is, all the objects and functions that are used need to be better organized, especially when it comes to big files but also overall. webMethods ActiveTransfer was born as an ESB to handle messages, and these messages were typically very short, i.e. small in size. A message is data that you have to send to an application, where it must be received in real-time and possibly processed or acknowledged elsewhere in the system as well. So, because it was initially designed for small messages, it struggles with performance when presented with very large files. All this to say, I suggest that they have an engineer reevaluate the architecture of the product in order to consider cases where large files are sent, and not only small ones. As for new features, compared to other products in the market, I think Software AG should be more up to date when it comes to extra protocol support, especially those protocols that other solutions have included in their products by default. Whenever we need to add an unsupported protocol, we have to go through the effort of custom development in order to work with it. Also, all the banks are obligated to migrate to the new standards, and big companies are all handling translations and operating their libraries with the new protocol formats. But webMethods ActiveTransfer doesn't seem to be keeping up with this evolution. Thus, they should aim to be more compliant in future, along the lines of their competitors such as IBM and Primeur.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The product integration with Active Directory and detailed execution tracking for debugging are the most valuable features."
"The tool’s biggest benefit is the access we have to other Azure products."
"I am impressed with the tool's UI and analytics."
"The solution's best feature is that it is compatible with the cloud and has many connectors and third-party adapters."
"The product’s most valuable feature is integration."
"The most valuable feature of Microsoft Azure Logic Apps is the many available connectors that make automation easy. Additionally, the security of the solution is good."
"The prebuilt connectors available for SAP are really useful."
"The product's most valuable feature is scalability."
"ActiveTransfer lets us maintain the file in the staging area before we transfer it. After that, we can remove the file to make sure that the reconciliation process is done. Sometimes we will zip and unzip the files, but if we have a GKB file, we often ignore it."
"webMethods API Portal is overall very valuable. It is now a comprehensive API catalogue that serves various purposes, including API assessment and evaluation."
"There's hardware, software and application integration, providing hosting flexibility."
"I like the tool's scalability."
"The synchronous and asynchronous messaging system the solution provides is very good."
"The most valuable feature of the webMethods Integration Server is the built-in monitoring, auditing, RETS, and SOAP services."
"The performance is good."
"Our use case is for integration factory for SAP. It is mostly for SAP integration."
 

Cons

"Standard documents are fine, but in certain situations, when facing specific errors or issues, partners or consumers expect customized solutions rather than just links to existing documents."
"An area for improvement for Azure Logic Apps could be enhancing its ability to handle large datasets. When dealing with extensive data, we often have to use Azure Data Factory, which is mostly limited to scheduled jobs."
"Pricing and handling asynchronous processes are the two main areas that need improvement."
"There could be more AI features included in the product."
"The solution could add an AI version to make it easier for people."
"Microsoft Azure Logic Apps can improve by continually updating the connectors to make them better."
"The product should integrate more APIs"
"It's for a limited kind of application or short Apps. And, not for the complex applications."
"Rules engine processes and BPM processes should be improved."
"This solution could be improved by offering subscription based licensing."
"The improvement needed is related to the model's position. As of now, it seems to be more of a conceptual idea rather than a widely implemented solution. For how long"
"The initial setup of the webMethods Integration Server is not easy but it gets easier once you know it. It is tiresome but not difficult."
"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."
"webMethods Integration Server needs to add more adapters."
"There should be better logging, or a better dashboard, to allow you to see see the logs of the services."
"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."
 

Pricing and Cost Advice

"The tool’s pricing could be better."
"If we are comparing to other public cloud vendors, such as Amazon or Google Cloud platform, I wouldn't say that it's expensive. However, when we're comparing between a host such as GoDaddy or Digital Ocean, then it's a bit on the expensive side."
"The product is not cheap. I would rate the product's pricing a five out of ten."
"The product pricing aligns well with the value and capabilities offered by Azure services."
"I rate Microsoft Azure Logic Apps's pricing a seven out of ten."
"The licensing is cheaper because, compared to other services, Azure services are much cheaper and affordable."
"Microsoft Azure Logic Apps could be costly if a user isn't careful. The costs associated with the solution could still be improved."
"In my experience, Microsoft Azure Logic Apps is not a cheap solution."
"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."
"This is an expensive product and we may replace it with something more reasonably priced."
"The vendor is flexible with respect to pricing."
"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."
"There are no hidden costs in addition to the standard licensing fees for webMethods. For corporate organizations, it's a very cheap or fairly priced product, but for growing or small businesses, it's quite expensive. These businesses would probably need to consider an enterprise services bus at some point. Thus, from a pricing point, it closes out non-cooperate businesses."
"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."
"There is a license needed to use the webMethods Integration Server."
"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."
report
Use our free recommendation engine to learn which Integration Platform as a Service (iPaaS) solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
38%
Computer Software Company
9%
Manufacturing Company
6%
Government
5%
Financial Services Firm
13%
Computer Software Company
13%
Manufacturing Company
13%
Energy/Utilities Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Microsoft Azure Logic Apps?
The solution's most valuable feature is the no-code/low-code feature.
What is your experience regarding pricing and costs for Microsoft Azure Logic Apps?
The pricing is very clean and transparent. You can start small and pay only for what you use. There are no upfront licensing costs or contracts you are bound to.
What needs improvement with Microsoft Azure Logic Apps?
The business rules engine is still not fully developed, and it would be very helpful to see improvements here.
What do you like most about Built.io Flow?
The tool helps us to streamline data integration. Its BPM is very strong and powerful. The solution helps us manage digital transformation.
What is your experience regarding pricing and costs for Built.io Flow?
webMethods.io is expensive. We have multiple components, and you need to pay for each of them.
What needs improvement with Built.io Flow?
webMethods.io needs to incorporate ChatGPT to enhance user experience. It can offer a customized user experience.
 

Also Known As

Azure Logic Apps, MS Azure Logic Apps
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Learn More

Video not available
 

Overview

 

Sample Customers

nord lock, mission linen supply, esmart systems
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about Microsoft Azure Logic Apps vs. webMethods.io and other solutions. Updated: December 2024.
831,265 professionals have used our research since 2012.