Microsoft Azure Logic Apps vs webMethods.io comparison

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

"It is a very stable solution."

"I like the ability within Logic Apps to design the workbooks through the portal with minimal code."

"The product’s most valuable feature is integration."

"The product's initial setup phase is something that I don't think is complex because once we start using it, it becomes simple."

"The Logic App's designer is one of the vital features"

"It's very easy to use, and it's blazing fast. The best thing about Logic Apps is actually its ability to create a solution in a matter of hours. It doesn't need any kind of provisioning, and you don't need any kind of hardware. You can create very small elements like these Logic Apps, and you can build a whole solution from those very simple and small elements. I also like that they are completely incorporated with your existing active directory. You can use user groups directly from the active directory inside Azure and access it from the Logic Apps. You don't need to do anything special, and you just have access. You can just check if the user is, for example, allowed to do some action. Normally it would take you some additional steps and some additional calls to check it. You have to come back to the active directory to make this possible. In Logic Apps, you just have it, and you can use it. I think that there's this concept of logging and recall to the Logic App. It shows you every single step, every single product, and the result it's returning to the next step. It also has an amazing debugging feature. You can rerun some calls and see if, after a correction of the Logic App, for example, you get the correct results. So, it's almost like it's alive. It's like you make a change, poof it, and it's in production, and it's working. The speed of the composition of the problem and creating a real solution for it is extremely fast with this solution. It's extremely fast in creation."

"Its integration capabilities are great, allowing connectivity with various applications and services."

"The ease of mapping... is the single largest feature. It gives us the ability to craft anything. A lot of single-purpose technologies, like Mirth, are good for healthcare messages, but we use webMethods not only for healthcare messages but for other business-related purposes, like integrations to Salesforce or integrations to Office 365. It's multi-purpose nature is very strong."

"Some of the key features are the integration platform, query mechanism, message handling within the bus, and the rules engine. We've had a really good experience with webMethods Integration Server."

"Currently, we're using this solution for the integration server which helps us to integrate with the mainframe."

"The solution's ease-of-use is its most valuable feature, in which complex issues may be resolved."

"webMethods platform is used to build an EAI platform, enabling communication between many internal systems and third-party operators."

"The tool supports gRPC."

"Application integration, business process integration, and B2B partner integration are valuable. But among these, I feel B2B partner integration is the most valuable. This module integrates two business partners and exchanges data through electronic data interchange messages in the form of specific standards, without any manual process needed."

"webMethods Integration Server is an easy-to-use solution and does not require a lot of coding."

"It would be beneficial to have less code and tighter integration between different cloud services."

"The business rules engine is still not fully developed, and it would be very helpful to see improvements here."

"The support I have received is mixed because in some cases they are accurate, and in others, it was me doing the groundwork and giving feedback for the agent to finally tell me there is an issue in their larger services."

"The visual tool that is used to build integration is quite old."

"The standard logic app could be simplified. Thats what we would like to see in the next release."

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

"I find the current interface useful, but I could see how others would want the UI bits that are used for creating Logic Apps to be simplified."

"The solution should include more connectors."

"As webMethods Integration Server is expensive, that's its area for improvement."

"Understanding the overall architecture is difficult."

"It is quite expensive."

"The on-premises setup can be difficult."

"When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods."

"The product must add more compatible connectors."

"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 configuring of the JWT token would be improved as it is a confusing process. We require more information on this part of the solution."

"The licensing is cheaper because, compared to other services, Azure services are much cheaper and affordable."

"It's very cheap, but it comes with pluses and minuses. The positive thing is that it's very cheap, but on the other hand, it's extremely hard to tell how much it will cost. At the start of the project, it's almost impossible to tell how many times you will be calling some kind of Logic App function. You cannot state how much of the internet transfer you will use or how much data your will use."

"Microsoft Azure Logic Apps is a little bit expensive, and that is why you use it only for certain types of scenarios."

"Compared to the prices of Mulesoft, the price of Microsoft Azure Logic Apps is low."

"The pricing is not expensive."

"The product is quite cheap."

"The cost of the solution could be cheaper."

"I would rate the pricing a six out of ten"

"The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product."

"The pricing is a yearly license."

"This is an expensive product and we may replace it with something more reasonably priced."

"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."

"webMethods Trading Networks is a bit costly compared to others solutions."

"The price of webMethods Integration Server isn't that high from an enterprise context, but open-source ESB solutions will always be the cheapest."

"Some who consider this solution often avoid it due to its high price."

"I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."