Microsoft Azure Logic Apps vs webMethods.io comparison

"Easy to use and is able to integrate with other Azure-based environments."

"Logic Apps helped reduce complexity or development time. For example, if we get documents in the form of images, we can use Logic Apps to extract information from those images. This simplifies our efforts compared to originally using Microsoft APIs to do the same task."

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

"The solution has plenty of good valuable features and a plethora of services."

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

"The solution's most valuable feature is the no-code/low-code feature."

"The product's most valuable feature is scalability."

"It's easy to use, and it's stable."

"I like the solution's policies, transformation, mediation, and routing features."

"webMethods API Portal is overall very valuable. It is now a comprehensive API catalogue that serves various purposes, including API assessment and evaluation."

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

"The messaging part is the most valuable feature."

"The most valuable feature of webMethods Integration Server is all the capabilities it provides. We leverage most of the features, that they have offered to us. Our vendor has made some additional features on top of the webMethods Integration Server and we use all the features together."

"This solution has given us a competitive advantage because we have better automation and insight."

"The tool is very powerful and user-friendly."

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

"It's for a limited kind of application or short Apps. And, not for the complex applications."

"It can be a bit challenging to use."

"The stability of Microsoft Azure Logic Apps is stable. However, we have had some issues in the past. They do resolve issues that arise from new releases."

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

"The product needs improvement in getting direct access to the code and versioning."

"We wanted to use Microsoft Azure Logic Apps, but we faced a timeout."

"An area of improvement I've encountered is related to the number of connectors available in Logic Apps. While there are many connectors, I found that the "send email" connector may not work as expected, and one has to rely on Office 365 plugins or other alternatives. This could enhance user experience, especially when considering the additional overhead and licensing requirements associated with Office 365. It also needs to improve security features."

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

"Technical support is an area where they can improve."

"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."

"This product has too many gaps. You find them after update installations. This should be covered by automatic testing."

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

"With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."

"We'd like for them to open up to a more cloud-based solution that could offer more flexibility and maybe a better rules engine or more integration with rules engines."

"The solution's release management feature could be better."

"With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."

"The price of Microsoft Azure Logic Apps is inexpensive."

"The product pricing aligns well with the value and capabilities offered by Azure services."

"The pricing is not expensive."

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

"Microsoft Azure Logic Apps could be costly if a user isn't careful. The costs associated with the solution could still be improved."

"The pricing is okay. It's not highly priced. It's in the medium range."

"The product is quite cheap."

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

"It is worth the cost."

"The price is a little bit high, especially regarding their support."

"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."

"The solution’s pricing is too high."

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

"Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under."

"Initialy good pricing and good, if it comes to Enterprise license agreements."

"Always plan five years ahead and don’t jeopardize the quality of your project by dropping items from the bill of materials."