We performed a comparison between IBM API Connect and OpenLegacy 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."This product is well integrated with other products. Its ability to interact with IBM Secure Gateway and other integration products is the core feature. Also, the lead time to put it into production is relatively short ."
"It is a complete all-in-one solution."
"API Connect's data gateway is one of the strongest in the market."
"WSRR is a powerful component for getting the endpoints."
"The product gathers data to measure API performance."
"The most valuable feature for me is the ability to distribute work among our API developers, so we don't have to do all the work as IBM API Connect administrators and IBM DataPower administrators."
"It offers enhanced security features to protect APIs, enforce access control, and secure sensitive data."
"The services that I consume through IBM API Connect are beneficial. It can handle multiple API management."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"Opens the door to connect modern web products to an old legacy system."
"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."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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."
"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."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"In terms of what needs improvement, some of the product documentation could be better."
"One thing about API Connect that could be improved is the security schemes. There are so many security schemes, and from a product perspective, IBM could improve the user experience of the configuration security scheme."
"Support for this platform could still be improved. It also needs to have more levels of versatility. Its compatibility and integration with different platforms also need improvement."
"Components, like caching, should be implemented as policies, not requiring dependency on an external solution."
"It's based on a little bit dated architecture. A lot of evolution has happened after that. It's an evolving field. Kong is a Kubernetes-based platform. Kong runs on Kubernetes, but all the other ones are in microservices. So, there's a lot of improvement that can be done."
"The new version is very unstable."
"Like any typical IBM infrastructure setup, you need to learn to set it up yourself. It's not one of those simple zip files or an archive unzip and you're up and running in some few minutes. Knowledge to set it up is key."
"It would be helpful to have access monitoring."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"Debugging and logging for programmers could be better."
"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."
"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."
"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."
"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."
Earn 20 points
IBM API Connect is ranked 5th in API Management with 73 reviews while OpenLegacy is ranked 37th in API Management. IBM API Connect is rated 8.0, while OpenLegacy is rated 7.6. The top reviewer of IBM API Connect writes "Offers basic API orchestration and provides robust security and governance features". On the other hand, the top reviewer of OpenLegacy writes "The biggest advantage is how simple the technology was". IBM API Connect is most compared with IBM DataPower Gateway, Apigee, Microsoft Azure API Management, MuleSoft Anypoint API Manager and Amazon API Gateway, whereas OpenLegacy is most compared with Kong Gateway Enterprise 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.