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."WSRR is a powerful component for getting the endpoints."
"API Connect's most valuable feature is its ability to act as a gateway. It's very easy to configure security and everything else in it. You don't have to kill yourself implementing custom configurations."
"The interface is very nice. It makes the solution easy to use and navigate."
"It is a complete all-in-one 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."
"The most valuable feature is the security we get from this solution. I know of a bank that uses it to ensure that everything is secure. The second feature I like is the retail environment, where we actually want to be able to provide as many suppliers and consumers with APIs as possible. If you are well-trained in the writing of RESTful API's, you can actually publish an API in a matter of minutes, test it, and publish it."
"The developer portal has been the most useful feature."
"The ability for all of our web applications to share standard functions and documents easily is valuable."
"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."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"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."
"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."
"Documentation for the CLI is not very complete. Also, the support could be improved, and we have had several problems with backing up and restoring the product."
"It would be helpful to have access monitoring."
"Extracting the data could be improved."
"We ran it on top of the Kubernetes cluster, so it wasn't a standalone service. In the worst-case scenario, API Connect couldn't stay online if all the containers went down. We had to restart all the services. We shut down all the containers automatically one by one."
"The new version is very unstable."
"There is room for improvement regarding the connectivity of the DevOps."
"Possible improvement is mainly around having more of the cloud oriented architecture bringing stability in adding new capabilities around security."
"The initial setup and installation could be easier."
"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 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."
"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."
"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."
"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.