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."The most valuable features of Layer7 API Management are integration, ease of use, building APIs easily, and portal straightforward."
"The speed and versatility in the implementation of APIs without writing a line of code in any programming language."
"We can get more visibility into our data."
"The solution has numerous configuration options to increase security in communication."
"I work for an information security company. CA API Management is capable of using tokens for authorization to manage access control for the APIs."
"Layer7 API Management's availability on an on-premises deployment model, actually decreases the production time if its users have any issues at the server level."
"The product supports more than just HTTP protocols; it also caters to JMS and FTP protocols."
"There are a couple aspects of performance. One is just speed and uptime, and it's stellar in that regard. The other is, how much effort is it to put it in place in the first place, and then how much effort is it to keep it operational. That's where its real strength is. I'm able to do things quickly and easily that I couldn't do before."
"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."
"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 connect a service to a mainframe program or back transaction in a matter of minutes or hours at the most."
"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 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."
"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."
"OpenLegacy produces a war file which includes everything you need to deploy a Tomcat server."
"I would like for the new release to allow us to speed up code generation. The integration with CICD could also be more seamless."
"The solution should prioritize ease of use and align with the growing trend of cloud-native environments."
"The delivery is bulky in terms of implementation. Its price could also be better. It is a very good product as compared to CA API, Google API, and WSO2 API, but its price is high. From the cloud-native perspective, some new features need to be added. It could also be made simpler to implement."
"The developer portal needs to fully supported SOAP services (including WSDL publication with security), it would certainly push adoption for us."
"There is still room for improvement for the CA API Developer Portal. It is still not on par with what the competencies are."
"Needs to work better with DB2 UDB."
"The initial setup was very complex."
"As a SaaS product, control over some configuration elements and environments is lost."
"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."
"Debugging and logging for programmers could be better."
"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."
Earn 20 points
Layer7 API Management is ranked 10th in API Management with 110 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, MuleSoft Anypoint API Manager, Amazon API Gateway 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.
