Amazon API Gateway vs webMethods.io comparison

"The solution is user-friendly."

"What I like best about Amazon API Gateway is that it's simple to use, easy to set up, and you can quickly get it up and running. It's a very user-friendly solution. I also didn't experience any issues in terms of Amazon API Gateway interface, integration, or monitoring. The solution runs smoothly."

"It's a low-code solution that helps our company manage operations seamlessly"

"The most valuable feature of the solution is that it is a stable solution with an uptime of 99.99 percent."

"The product is really good when it comes to API lifecycle management, and it is not just something that includes the balancing part or the security aspect but also the routing and the fallback mechanism."

"It allows us to expose our APIs and provides tools for managing them."

"The solution is solid, robust, and scalable."

"It is easy to set up. It is also quick to deploy."

"I like the tool's scalability."

"It is good for communicating between the systems and for publishing and subscribing. We can easily retrieve data. It is good in terms of troubleshooting and other things."

"I like the stability of the webMethods Integration Server."

"The most valuable feature is stability."

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

"The solution has a very comprehensive and versatile set of connectors. I've been able to utilize it for multiple, different mechanisms. We do a lot of SaaS and we do have IoT devices and the solution is comprehensive in those areas."

"From a user perspective, the feature which I like the most about Integration Server is its designer."

"We can arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant cachings and integrations, as well as and also load permitting."

"The solution could improve signature validation."

"API Gateway lacks some governance features that MuleSoft offers, and there are additional features that could make it even better."

"There are features lacking in API Gateway, such as the timeout settings, which currently are set at 29 seconds."

"The user interface could be improved, as well as customer support and having a local customer representative in a country."

"The integration could be improved."

"Since the first invocation of AWS Lambda takes more than 30 seconds because of Lambda's cold start, Amazon API Gateway blocks that resource, thereby aborting the invocation."

"Amazon API Gateway needs to focus on minimizing latency."

"When using APIs, the manual bit for intermediate confirmation with VTL can be a challenge."

"The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that."

"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."

"I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier."

"Some things could be improved, especially how ActiveTransfer handles third-party file transfers. It would be nice to have a native file-watching mechanism for when you're scheduling jobs with a third-party scheduler. Currently, we are using an outside file watcher solution to check the files before the file transfer. It checks the location to see if the file is there. If the file is there, it will prepare it for transfer. If the file isn't available, it will send an email it can create a ticket send it now. We recommended adding this file watcher mechanism."

"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."

"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 on-premises setup can be difficult."

"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."

"The product is expensive."

"Amazon API Gateway is a very cheaply priced product."

"Fees are volume-based."

"Since it's a serverless solution, Amazon API Gateway is not so expensive."

"There are no licensing fees."

"Azure products are more cost-effective than AWS solutions"

"The solution's pricing is cheap and based on the number of requests coming to Amazon API Gateway."

"It is somewhat costly, particularly when it introduces server-related features, which are often scheduled on our end."

"Its cost depends on the use cases."

"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."

"I signed a three-year deal with them. It is a yearly locked-in price for the next three years."

"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."

"Most of my clients would like the price of the solution to be reduced."

"It is worth the cost."

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

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