Try our new research platform with insights from 80,000+ expert users

Layer7 API Management vs OpenLegacy comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Layer7 API Management
Ranking in API Management
11th
Average Rating
8.4
Number of Reviews
110
Ranking in other categories
No ranking in other categories
OpenLegacy
Ranking in API Management
35th
Average Rating
7.6
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2024, in the API Management category, the mindshare of Layer7 API Management is 3.2%, down from 3.2% compared to the previous year. The mindshare of OpenLegacy is 0.2%, down from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Ronald D'Souza - PeerSpot reviewer
May 15, 2023
Has great drag-and-drop features and it requires minimal coding
I have mainly implemented using Layer 7 API Management. Some of the major challenges we were able to meet with a quick release to market methodology. Some of the tasks which we achieved for our customers were: 1. Translation service from SOAP to REST and vice versa. 2. API service to DB (Oracle, MySQL, MSSQL, Snowflake, SAP HANA) -- Created Swagger APIs that were able to perform CRUD operation to the backend API mentioned above and provided routes to query and get data. 3. Integration with Payment gateway service providers to perform (transaction on behalf of the customer with third-party payment gateway service providers white labeled with our APIs ) -- Followed TMF standards for payment gateway integration with the Telcom world. 4. Orchestration of the API. Build multiple microservers and provided orchestration based on route, path, and data in the request and perform actions that would be communicated with multiple APIs and provide a single consolidated response. 5. Provided API-driven security (Oauth 2.0, JWT, SAML, Basic, and a variety of means) to access the API giving the developer the freedom to concentrate only on application/service/microservice and let the gateway handle the threat. 6. Seamless Mutual Authentication allowed good segregation between APIs in the DMZ and internal network.
KK
Nov 10, 2021
The biggest advantage is how simple the technology was.
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. OpenLegacy handles the bread-and-butter TP monitoring stuff, but I am working for one of the six banks in the United States still using the Hogan mainframe, which has a slightly proprietary mechanism. But OpenLegacy currently doesn't have a connector for Hogan. So it would help if they could build one. That would appeal to financial institutions that still use Hogan, like US Bank, Wells Fargo, KeyBank, and Vanguard.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It is flexible in how it creates custom policies and uses builds with impressive methods."
"It has improved API governance and gives analytics to API performance."
"It is able to withstand the number of API calls and handle different API requirements to secure, transform, log, and track API usage patterns."
"We loved the portal part the most, which had monetization and showed how people were using the stuff. It is a good product as a whole and has a lot of microservices and granular features."
"It can be scaled as we need. And it can be used in different regions. We have different data centers in the U.S. and Beijing. We use it on-premise, on-cloud, and it can be hosted and used at any place and scaled across the regions."
"This improved our organization, because it gives the management data to discuss for the next course of action and it suggests what to work on, as the next thing."
"They have got a very compelling platform that enables organizations to easily develop and roll out mobile applications."
"Security is the most important parameter of the solution, for me, because whenever you are exposing your APIs to third-parties, it is critical that the data remains anonymous and that data is retained within the system, that it is not leaked. CA API Management provides good security features."
"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."
"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."
"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."
"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."
 

Cons

"Broadcom's technical support team needs improvement."
"The Portal lacks maturity. Since the move from Portal 3.x to 4.x, a lot of features were removed. It is slowly coming back. I can see a lot of changes are done in the "background" to decouple components and make it more flexible. Those changes are just not getting to the UI side quick enough."
"There are old algorithms that the tool does not support - and it shouldn't, in my opinion. But sometimes customers need old algorithms, from old use cases and old applications, migrated to the platform. At those times, there are hiccups that happen."
"The architecture of the solution does not allow for flexibility in using different components for the gateway architecture."
"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."
"I feel there is a lot to improve in terms of providing plug-and-play functionalities, as at the moment it requires a lot of coding in their specific language for implementing a medium-complexity use case."
"The interface is Java which is difficult to make look very nice."
"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."
"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."
"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."
 

Pricing and Cost Advice

"There are various licensing models for Layer7 API Management. We have to buy additional licenses to get new versions."
"It has a reasonable pricing model by instance."
"Pricing is competitive. CA is ready to offer attractive discounts."
"The price of Layer7 API Management is too high and should be reduced. However, it is a good solution in the market."
"APIs can be developed to provide security. We can show them in one single pane of glass, such as the CA API Management API Developer Portal. It is there that we can provide the monetization for their APIs and what is happening on third-party applications, like Paytm or BookMyShow."
"It is a pricey product, although not extremely overpriced compared to competitors in the market."
"Licenses are required to operate the product, but I don't know much about the validity periods attached to it."
"It's my manager who takes care of the pricing. But I keep on hearing that it's a little pricey, it's on the higher side. That is what he says."
"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."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
814,649 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
14%
Manufacturing Company
9%
Government
7%
Financial Services Firm
36%
Computer Software Company
11%
Insurance Company
11%
Real Estate/Law Firm
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Layer7 API Management?
Licenses are required to operate the product, but I don't know much about the validity periods attached to it.
What needs improvement with Layer7 API Management?
Layer7 API Management should have more stability towards the operating system. I think we were planning to go to version 11, and then Layer7 API Management said you need to move from CentOS to some...
Ask a question
Earn 20 points
 

Also Known As

CA API Management, CA Live API Creator, Espresso Logic, CA API Gateway
No data available
 

Overview

 

Sample Customers

1. IBM  2. Microsoft  3. Oracle  4. Salesforce  5. SAP  6. Cisco  7. Dell  8. HP  9. Adobe  10. VMware  11. Accenture  12. Capgemini  13. Deloitte  14. PwC  15. Ernst & Young  16. Infosys  17. TCS (Tata Consultancy Services)  18. Wipro  19. Cognizant  20. HCL Technologies  21. Tech Mahindra  22. Fujitsu  23. Hitachi  24. NEC  25. NTT Data  26. Ericsson  27. Nokia  28. Siemens  29. AT&T  30. Verizon  31. Vodafone  32. Orange
Many of openLegacy's global customers are among the Global 100 companies. Review case studies in these industries: Agriculture, Airport Authority, Automotive, Auto, Finance, Insurance, Government, Healthcare, Manufacturing, and Retailwww.openlegacy.com/case-studie...
Find out what your peers are saying about Layer7 API Management vs. OpenLegacy and other solutions. Updated: October 2024.
814,649 professionals have used our research since 2012.