We performed a comparison between OpenLegacy and webMethods.io API based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Google, Amazon Web Services (AWS) and others in API Management."Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"The biggest advantage of OpenLegacy was how simple the technology was. We were able to build out the OpenLegacy parts very quickly. We put together a couple hundred APIs in six months."
"Opens the door to connect modern web products to an old legacy system."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"Using OpenLegacy, the exposure of services is far easier and quicker. In many cases, exposure of services requires just a few clicks and takes only minutes. In very complex cases, it still only takes half a day. Without OpenLegacy, it would take us several months to create the same services."
"OpenLegacy provides a way to go from the outside world to the legacy mainframe, to move the old standard application to a REST API application. New digital services can be created in a few clicks and this can be done easily by COBOL programmers."
"The performance is good."
"Clients choose webMethods.io API for its intuitive interface, promoting seamless interaction and quick communication between systems."
"I would like to see SSL out-of-the-box. OpenLegacy certainly does SSL, but it was not the default for our use case. We are currently working with OpenLegacy to cross the SSL bridge and suspect that most users will want to do the same."
"I'd like to see OpenLegacy develop its low-code/no-code (LCNC) solutions. They've expanded somewhat their horizons for integration beyond mainframe CICS, which is their sweet spot. They have some tooling in that area, but it's not as good as it needs to be."
"We would also be more than happy if the product had the option to work in the opposite direction – the ability to consume REST/SOW services in the outer world from the mainframe."
"Debugging and logging for programmers could be better."
"The pricing of the solution could be more flexible and allow for once-off payment versus annual licensing. This would be more appealing to companies in Latin America."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"I would like the solution to provide bi-weekly updates."
"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."
Earn 20 points
OpenLegacy is ranked 37th in API Management while webMethods.io API is ranked 30th in API Management with 2 reviews. OpenLegacy is rated 7.6, while webMethods.io API is rated 8.0. The top reviewer of OpenLegacy writes "The biggest advantage is how simple the technology was". On the other hand, the top reviewer of webMethods.io API writes "Offers a strategic toolset for gradual integration advancement". OpenLegacy is most compared with Kong Gateway Enterprise, IBM API Connect and MuleSoft Anypoint API Manager, whereas webMethods.io API is most compared with Apigee and MuleSoft Anypoint API Manager.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
