We performed a comparison between Apigee 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."Apigee provides out-of-the-box policies, so it is ready to use with minimal configuration to those policies. You can govern your API and manage the life cycle of the API completely with the Apigee tool."
"I'm still evaluating, but in terms of overall performance and stability, it's quite good."
"They capture the details of all the incoming and outgoing traffic of your APIs. Based on 300+ default dimensions you can generate beautiful and insightful reports on usage and consumption of APIs."
"It has a very efficient logging system which is easy to maintain."
"One of the best parts of this solution is the implementation as we did not need to use code or out-of-box policies. When it comes to the cloud-based architecture, there is a high level of reliability."
"I like implementing different policies, for example, rate-limiting policy."
"There are just a lot of security features in general."
"The stability of the solution is good. There aren't issues surrounding bugs or glitches. We don't find that it crashes or freezes. It's pretty reliable."
"It is possible to solve larger legacy API issues on an enterprise level with this product."
"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 mainframe programs (not screens), the OpenLegacy services do not require any changes by the mainframe programmers, thus reducing development cycles."
"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."
"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."
"The developer portal's adoption of the OpenAPI standard needs to be improved. In the latest version of the developer portal, they have adopted the OpenAPI standard. This feature, however, can be improved by supporting more characteristics of the OpenAPI standard."
"The pricing for the product was a bit higher. I also found it challenging to manage sometimes."
"They need to work on the cost of the solution."
"The initial setup is not straightforward, particularly for hybrid solutions."
"Sometimes there are glitches, which means there's still room for improvement in the platform."
"I don't have any notes for improvement."
"I would like to see better integration and some architectural improvements in future releases of the solution."
"The entire user across all the layers should be singly authenticated through an external authentication system."
"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."
"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."
"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."
"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."
Earn 20 points
Apigee is ranked 2nd in API Management with 82 reviews while OpenLegacy is ranked 37th in API Management. Apigee is rated 8.2, while OpenLegacy is rated 7.6. The top reviewer of Apigee writes "Has a robust community and outstanding performance". On the other hand, the top reviewer of OpenLegacy writes "The biggest advantage is how simple the technology was". Apigee is most compared with Microsoft Azure API Management, IBM API Connect, Amazon API Gateway, WSO2 API Manager and MuleSoft Anypoint API Manager, whereas OpenLegacy is most compared with Kong Gateway Enterprise, IBM API Connect 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.
