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."We really like the runtime capabilities of IBM API Connect. The creation of products and the control of the monetization and hit rate are some of the features which we've found very valuable."
"In-built policies and security functions."
"It allows enterprises to expose some of their tech to outside stakeholders."
"IBM API Connect is a reliable and scalable solution."
"It is a complete all-in-one solution."
"It's quite flexible and easy to deploy, especially for beginners. It has almost all the features that an API gateway should have."
"API Connect is a good product, and everything works fine. All the analytics are good, and it is easy to follow up. I like it in that sense. I'm more focused on following up on analytics by seeing how many API calls we are getting and where we see a lot of problems. I was working on that API level."
"Our version supports containerized integration. I can write APIs, which can be moved into a testing environment without needing a forklift. It can check if APIs are compliant before moving them into production."
"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 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 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."
"Opens the door to connect modern web products to an old legacy system."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"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."
"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."
"We would have more capability to interact with the catalog and inventories, so a more DevOps-friendly solution is needed."
"API Connect's analytics subsystem could be improved to make it easier to render content from the analytics system and offload it to an external database."
"I would like to see automation of the installation. If there could be a single-click function where you could automate everything, that would be helpful."
"There are issues with upgrading in the cloud version. The cloud version is extremely buggy. We prefer to use the on-premise version."
"It would be nice to have a SaaS solution that can be deployed into the cloud."
"It should be cheaper."
"Due to bugs in integration, we have to look for workaround on fixing and using DataPower as gateway."
"The installation process could use improvement. I hope that in the next release, the installation process is easier."
"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."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"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."
"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."
"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 "Good speed and performance, but it's based on a bit dated architecture". 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 Apigee, IBM DataPower Gateway, 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.
