Axway AMPLIFY API Management vs webMethods.io comparison

"In general, API governance provides a better experience for providers."

"The administration tool for this solution is good."

"The API portal capability is a valuable feature."

"The most valuable feature of the solution is security."

"The most valuable features are security enforcement and throttling."

"There's drag and drop functionality so that you do not need to have a senior expert developer to make use of the tool. You can get more of your staff trained up to be able to use it as it's not overly technical."

"This product is a ten when it comes to API management."

"We like the portal for documentation a lot."

"webMethods Trading Networks is a good solution for interacting with outside of the organization. We can integrate the solutions with multiple outside the organization."

"The most valuable feature of the webMethods Integration Server is its reliability. It has a lot of great documentation from the service providers. Additionally, it is easy to use."

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

"One [of the most valuable features] is the webMethods Designer. That helps our developers develop on their own. It's very intuitive for design. It helps our developers to speed the development of services for the integrations."

"webMethods Trading Networks is a stable solution."

"The developer portal is a valuable feature."

"I feel comfortable using this product with its ease of building interfaces for developers. This is a better integration tool for integrating with various applications like Oracle, Salesforce, mainframes, etc. It works fine in the integration of legacy software as well."

"Application integrations are offered out-of-the-box, and that is extremely important to us. This is one of the main use cases that we have for it. It is about 60 to 70 percent of the workload in our application today."

"It would be great if they have an asset report. It's hard to get support for that."

"This solution does have some limitations regarding the deployment model."

"The installation process is a bit complex and it could be a lot simpler."

"The API Mocking tools need to be improved."

"In terms of customer service, the company needs to be easier to contact, and the support team needs to understand the situation and the product itself better."

"Sometimes we find bugs where certain calls are not returning all the data we need."

"Team management capabilities could be improved."

"The areas for enhancement should be improving certain filters within the solution. Although they are generally functional, there are occasional problems that could be more precisely adjusted. Additionally, the solution performs well within its workload limitations, but it may not be suitable for scaling up or managing a larger volume of transactions through the gateway. To address this, it may be necessary to adopt a unique architecture rather than relying on traditional pre-packaged options."

"This solution could be improved by offering subscription based licensing."

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

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

"Perhaps in the area of Microservices, where I think Trading Networks could benefit from some improvements."

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

"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."

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

"The solution is expensive. When you acquire a license you have full access to the solution, unlike other competitors such as Apigee X, where there are fragmented licenses. Some licenses only allow access to certain features while others allow access to more features. Upon procuring this solution's license, you will have full access to the solution, allowing you to experiment with all of its features."

"Its cost depends on the use cases."

"The vendor is flexible with respect to pricing."

"I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors."

"It is worth the cost."

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

"Some of the licensing is "component-ized," which is confusing to new users/customers."

"It is a cost-effective solution."

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