We performed a comparison between Layer7 API Management 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."For developers to be able to come, sign up, or find APIs."
"It's a comprehensive tool that allows us to perform all the necessary tasks in one place."
"The Gateway is most important because it is our strategic front door into the company for all APIs."
"Initial setup is straightforward. It is simple and easy to do."
"It is fairly stable for the Gateway side."
"Key features include: lightweight mediation, transformation from JSON to XML and XML to JSON, API portal and API key management, the Developer Portal, and Circuit Breaker is a cool feature, too."
"Simple to use and easy to develop APIs."
"Mobile app capabilities is good for building mobile apps to consume developed APIs. Also, the API Portal capabilities are very nice, up to and including the ability to do monetization. Security features are exhaustive, with several adapters to all leading identity suites."
"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."
"It is possible to connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"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."
"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."
"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."
"Broadcom's technical support team needs improvement."
"As a SaaS product, control over some configuration elements and environments is lost."
"There is still room for improvement for the CA API Developer Portal. It is still not on par with what the competencies are."
"The UI design could be improved in the next release."
"It would be nice if we could create APIs directly from Swagger files. We're doing that ourselves with a middle layer. But if you could integrate with open API Swagger specs, and then just create a Swagger and upload it to the gateway and it would create all my API template policy, and would apply the OAuth restrictions, the types of security restrictions I have on there, that would be pretty cool."
"What is really important is that they offer the solution as a service, on a subscription or monthly basis, which will make it more attractive. That is where the market is headed. There are competitors within the industry that are doing that currently. I would encourage CA to do that."
"Provide complete documentation with examples of usage on its build in assertion/function."
"One day, where we can have a microservices gateway and we will not need the classic gateway at all, that is what we want to see."
"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."
"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."
"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
Layer7 API Management is ranked 10th in API Management with 109 reviews while OpenLegacy is ranked 37th in API Management. Layer7 API Management is rated 8.4, while OpenLegacy is rated 7.6. The top reviewer of Layer7 API Management writes "Has great drag-and-drop features and it requires minimal coding ". On the other hand, the top reviewer of OpenLegacy writes "The biggest advantage is how simple the technology was". Layer7 API Management is most compared with Apigee, Kong Gateway Enterprise, Amazon API Gateway, MuleSoft Anypoint API Manager and Microsoft Azure API Management, 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.
