We performed a comparison between Apigee, 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."It is easy to set up. It is on Google Platform, and there are multiple deployment models they support, which is great."
"This is a front-layer gateway that helps to improve our overall performance."
"It is scalable."
"It accelerates development and deployment processes."
"API/proxy lifecycle workflow for API providers is quite good and one of Apigee's strongest features."
"Apigee makes proxy management very simple."
"We use it to build API proxies for securing targeted back-ends with an emphasis on Continuous Integration/Continuous Development (CI/CD)."
"The most valuable features of Apigee for me are analytics, security, ease of use, and integration capabilities."
"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 capabilities are very good."
"The statistics component is easy to use."
"It is a complete all-in-one solution."
"The gateway is the most valuable aspect of this solution."
"Scalable and stable API platform for creating and managing APIs."
"It acts as a central gateway for both external APIs and underlying systems. It's basically a central middleware for hosting APIs to the internet and consuming APIs from internal systems. It provides central governance for any APIs going outside the network, ensuring security and a common contract for API definitions."
"This is a very easy to use solution."
"Using mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"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 solve larger legacy API issues on an enterprise level with this product."
"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 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."
"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."
"Drag and drop of features would be more beneficial, rather than manually working on the configuration and updates."
"There should be an integrated continuous integration and continuous deployment approach with Apigee. Currently, for development at a more integrated level, you have set it up yourself."
"I would like to see the monitoring, dashboards, and reports improve."
"Apigee lacks market presence."
"Apigee is not a solution compatible with public clouds, making it one of its shortcomings where improvements are required."
"We are experiencing issues with automation; the production in Apigee is quite time-consuming."
"The solution’s scalability could be improved."
"I have heard there maybe be some security issues that need to be addressed. If this is the situation I would encourage taking a look at the security matters."
"Extracting the data could be improved."
"The documentation needs to be a bit better."
"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."
"Different versions of the same thing can mean unnecessary duplication."
"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."
"IBM API Connect could improve the security of the application and the integration."
"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."
"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."
"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."
"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."
Earn 20 points
