Axway AMPLIFY Application Integration vs webMethods.io comparison

"The most valuable feature is that API Gateway is extremely flexible for any feature, such as connecting to Active Directory to pull the users and their authentication information. There are three ways to connect to Active Directory, and the reason for this is that the computing environments of our customers are very different. Every feature in API Gateway has got multiple methodologies for accomplishing those tasks, which is important because customers are constantly changing their security models, IT models, networks, etc. API Gateway is very flexible. It is not a one size fits all sort of situation where it is very rigid, and you can only use these pull-down menus, and that's all it ever does. It is much more open than that. It can give you fabulous reports on your users, usage, security issues, and the data sets that are going through there. You'll suddenly have visibility on the movement of data within or between your organization and other organizations. The other thing is that you're connecting API to API, which is machine to machine. The things that were done manually in an Excel spreadsheet before exchanging data through email are now done machine to machine and server to server. It speeds up the velocity of your business."

"Axway AMPLIFY Application Integration is very easy to use."

"The product is robust."

"Axway AMPLIFY Application Integration is quite a stable solution."

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

"It integrates well with various servers."

"webMethods Trading Networks is a stable solution."

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

"I would say the core Web-based integrations work the best. They are the most efficient and robust implementations one can do with webMethods."

"What I like best about webMethods Integration Server is its portfolio of connectors."

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

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

"The product must improve its visibility and scalability."

"Because it is so flexible, you really need someone who knows Axway Gateway or has been through the training and is certified. Just because you know APIs doesn't mean you're going to walk into that API Gateway and understand what to click on. If you're going to get something done quickly, you need to find an engineer from a company who has some experience with it. It is easy to learn, but if you're doing on-the-job training, it is going to take you longer to get your project accomplished."

"The most important point to improve is the capability to deploy in large enterprises."

"Axway AMPLIFY Application Integration is an expensive solution."

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

"The orchestration is not as good as it should be."

"t doesn't represent OOP very well, just a method and proprietary interface called IData."

"When it comes to scaling, it requires more RAM and more machines."

"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 deployment should be simplified."

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

"There should be better logging, or a better dashboard, to allow you to see see the logs of the services."

"API Gateway is priced on the number of transactions you run through it. API Gateway is free, and you can install as many API Gateways as you like or are necessary for your network. For example, if all of the data is inside your network or firewall, you may just need one API Gateway. If you have external customers trying to come into your organization through your firewall, you're going to need one API Gateway outside the firewall and one inside the firewall. If you have a lot of remote offices, you may want to put API Gateway in some of those offices as well. They only charge you for your usage of it. In other words, the number of transactions going through it. That's a good benefit."

"The product is not expensive."

"Users need to pay an annual licensing fee for the solution."

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

"This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."

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

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

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

"The solution's development license is free for three to six months. We have to pay for other things."

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

"The price is high and I give it a five out of ten."