Microsoft Azure Logic Apps vs webMethods.io comparison

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

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

"It is a very stable solution."

"Logic Apps is good for helping us run our access on a cloud environment like Azure. It's much easier, more reliable, and better to maintain."

"We can write external features and transfer the data using JPIMs securely which has been most valuable."

"We mainly used it to integrate SAP, ServiceNow, and different third-party APIs with the front end."

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

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

"In the API gateway, there is a new feature that allows us to filter logs within a payload. This has been a useful feature."

"The connectivity that the tool provides, along with the functionalities needed for our company's business, are some of the beneficial aspects of the product."

"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."

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

"The Software AG Designer has been great. It's very intuitive."

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

"Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."

"In Logic Apps, it supports AJAX and jQuery as commands to filter out to input the parameter. But regular expressions in general aren't supported well. So, I recommend that Logic Apps could be enhanced by supporting regular expressions (RegEx) more comprehensively ."

"There could be custom code for the product's components."

"Additionally, enhancing scalability features, such as implementing queuing mechanisms for high-concurrency scenarios, would greatly improve its utility."

"A room for improvement in Microsoft Azure Logic Apps is that it's expensive. Every step is going to cost you money, so if someone is not doing the steps carefully, at the end of the day, it will cost a lot of money. Each time you execute a step, the cost will depend on how much you use Microsoft Azure Logic Apps, and how many workflow steps you have. Each time a step needs to be executed, there'll be a cost added to your bill. If the developer isn't careful with how he uses the solution, this can blow up the cost. What I'd like to see in the next release of Microsoft Azure Logic Apps is for the cost and security to be better."

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

"Microsoft Azure Logic Apps could have more customization options for connectors."

"It would be helpful if the vendor could provide more data connectors."

"The pricing could be improved."

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

"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."

"Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion."

"It is quite expensive."

"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."

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

"The product must add more compatible connectors."

"The product is quite cheap."

"Logic Apps is cheap with its pay-as-you-go model. We only pay for usage time, no license fees. So Logic Apps is good in that aspect."

"It's a bit costly at the end of the day. It's difficult to calculate pricing, and that affects the business. That's one challenge."

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

"In my experience, Microsoft Azure Logic Apps is not a cheap solution."

"Its price depends on the number of transactions, storage capacity, etc., defining if the subscription will be monthly or weekly."

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

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

"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."

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

"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."

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

"There is a license needed to use the webMethods Integration Server."

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

"It is worth the cost."

"It is a cost-effective solution."