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."The management of the API and API portal is good."
"One of the most valuable features is the easy-to-use web interface."
"The most valuable feature of IBM API Connect is the security of the protocol."
"One of the most valuable features of this solution is that it protects our backend system. We are exposing services to external parties and using this solution to protect the backend system, and to have a navigation in between."
"Security is well organized and managed within the solution."
"It is quite stable. We've not had any problem. It has made for a good buy because we are finding that other companies that have similar set ups go down maybe once a month."
"It is a very scalable solution."
"It offers enhanced security features to protect APIs, enforce access control, and secure sensitive data."
"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."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"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."
"Opens the door to connect modern web products to an old legacy system."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"The developmental process is not quite user-friendly."
"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."
"Possible improvement is mainly around having more of the cloud oriented architecture bringing stability in adding new capabilities around security."
"It would be helpful to have access monitoring."
"Debugging could be improved."
"Installation is weak."
"I would like to see support for non-Java based services. We struggle a bit to be able to deploy and connect our .NET services because of things like data types. We had to map a couple of things. For one solution provider, we had to move them to .NET Core before we could use it properly. I would like to see more agnostic tool service platforms rather than moving it more towards Java or open source."
"The only disadvantage I can see is that it requires heavy hardware support."
"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."
"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."
"Debugging and logging for programmers could be better."
"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."
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.