Layer7 API Management vs OpenLegacy comparison

Read 5 OpenLegacy reviews

486 Views
322 Comparison Views

80% willing to recommend

Layer7 API Management

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 17, 2024

Layer7 API Management and OpenLegacy are two products competing in API management and legacy integration. Layer7 offers a comprehensive feature set, but OpenLegacy gains preference due to its unique focus on seamless legacy integration.

Features: Layer7 API Management is recognized for its robust security, traffic monitoring, and comprehensive policy management. It provides advanced security features like OAuth and access control. It supports integration with SiteMinder and offers excellent content-based routing abilities. OpenLegacy is known for rapid integration capabilities and the ease of extending legacy systems into digital frameworks. It allows the fast creation of APIs for existing legacy systems and offers straightforward deployment processes on platforms like Tomcat.

Room for Improvement: Layer7 could enhance its deployment processes, which could be time-consuming due to extensive configurations. Its user interface could be further optimized for simplicity. Additionally, the integration of newer technologies needs prioritization for better customer satisfaction. OpenLegacy might focus on expanding its documentation to accommodate varied levels of user expertise and could improve its analytics offerings. Compatibility with a wider range of legacy environments could significantly expand its user base while better support for non-standard APIs would be beneficial.

Ease of Deployment and Customer Service: OpenLegacy offers a streamlined deployment model and strong customer support which is highly responsive, aiding quick resolutions. This enhances its appeal for organizations focused on efficient legacy system integrations. In contrast, Layer7's deployment involves extensive configurations that might necessitate more time and effort. Its customer service, while supportive, may not match the promptness of OpenLegacy's support team.

Pricing and ROI: Layer7 API Management entails higher initial setup costs due to its extensive feature set but ensures a steady ROI through reinforced security and operational control. Conversely, OpenLegacy provides a more cost-effective approach with a significant ROI through reduced integration timeframes and the ability to leverage existing legacy systems. Its pricing model appeals to organizations emphasizing rapid integration and cost savings.

To learn more, read our detailed Layer7 API Management vs. OpenLegacy Report (Updated: December 2024).

Layer7 API Management vs. OpenLegacy

Download the complete report

Helped 824,067 peers since 2012

Categories and Ranking

Layer7 API Management

Ranking in API Management

10th

Average Rating

8.4

Reviews Sentiment

6.9

Number of Reviews

111

Ranking in other categories

No ranking in other categories

OpenLegacy

Ranking in API Management

34th

Average Rating

7.6

Reviews Sentiment

6.2

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of December 2024, in the API Management category, the mindshare of Layer7 API Management is 3.1%, 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

Presales Consultant for CA Southern Africa at Hyperion Holding Pty Ltd

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.

Read full review

reviewer1042905

VP, Chief Enterprise Integration Architect at a financial services firm with 10,001+ employees

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.

Read full review

Quotes from Members

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

Pros

"The solution has numerous configuration options to increase security in communication."

"It is fairly stable for the Gateway side."

"I love the API Gateway, especially the architecture, in terms of the composability of the policies. We approach it from a very software-engineering approach.We build on the policies, like legal blocks, and we deploy them throughout different environments. It's been working out great for us."

"The security checking authentication is our primary use case for this solution."

"The product documentation helps the client and/or user to evolve quickly while using the tool."

"The most valuable feature was the gateway because it has a good dashboard which shows all the hits, misses, and issues, how often you are viewing, what was the response time, etc. The gateway was very easy to deploy."

"Simple to use and easy to develop APIs."

"The Gateway can front our APIs very easily."

More Layer7 API Management pros

"Opens the door to connect modern web products to an old legacy system."

"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."

"It is possible to solve larger legacy API issues on an enterprise level with this product."

"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."

"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."

Cons

"They should incorporate deeper monitoring features into the solution to make the offering more complete. Doing so would help to showcase traffic patterns and usage to better engage customers and partners proactively. It would also help with API management and capacity planning."

"The solution should prioritize ease of use and align with the growing trend of cloud-native environments."

"The development toolkit used for creating APIs should be more online and user-friendly. Deployment and tracking could also be improved. Tools like Apigee provide a complete online experience along with RESTful APIs, to manage all activities. It is a very nice and user-friendly solution compared to CA."

"The security protocols in CA's product, for financial services, weren't as good as those in API Connect."

"There is a need for the migration of policies, better reporting, and monitoring integration."

"we cannot add gateways on the fly because there are a lot of moving parts; endpoint connectivity is one of them. If we add more nodes then the rate-limiting feature is affected. This kind of gateway always has the scalability issue. But, I think CA is coming up with its Microgateway, which is in Beta. If they stabilize their Microgateway platform, we could do very well in terms of scalability."

"The only issue we have is that we have to buy an APM license separately for end-to-end monitoring."

"The cloud-native architecture of the product needs improvement."

More Layer7 API Management cons

"Customer support for the product is slow and not very good. It makes using the product difficult if you need help quickly."

"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."

"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."

"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

"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."

"I think it's competitive. It's not that expensive when you compare CA with the Oracle product."

"It depends on your use case of course, how much you want to go with that, because it can get pricey and depends on the size of your company."

"The price of Layer7 API Management is reasonable compared to Apigee."

"It has a reasonable pricing model by instance."

"Licenses are required to operate the product, but I don't know much about the validity periods attached to it."

"This solution is a bit more expensive than competitors."

"I do not have experience with the pricing or licensing of the product."

More Layer7 API Management pricing and cost advice

"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."

See which vendors are best for you

Use our free recommendation engine to learn which API Management solutions are best for your needs.

See recommendations

824,067 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

19%

Computer Software Company

14%

Manufacturing Company

Healthcare Company

Financial Services Firm

34%

Computer Software Company

12%

Insurance Company

12%

Real Estate/Law Firm

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

Questions from the Community

What do you like most about Layer7 API Management?

The solution's technical support is good.

See all answers

What is your experience regarding pricing and costs for Layer7 API Management?

The pricing is expensive compared to other products.

See all answers

What needs improvement with Layer7 API Management?

Layer7 API Management could be improved in its logging and alert mechanisms. Furthermore, although cloud deployment has been introduced, I am not familiar with all recent updates. In previous versi...

See all answers

Ask a question

Earn 20 points

Comparisons

Apigee vs Layer7 API Management

Compared 33% of the time

Kong Gateway Enterprise vs Layer7 API Management

Compared 16% of the time

MuleSoft API Manager vs Layer7 API Management

Compared 16% of the time

Amazon API Gateway vs Layer7 API Management

Compared 11% of the time

Microsoft Azure API Management vs Layer7 API Management

Compared 6% of the time

More Layer7 API Management Competitors

Kong Gateway Enterprise vs OpenLegacy

Compared 42% of the time

MuleSoft API Manager vs OpenLegacy

Compared 23% of the time

IBM API Connect vs OpenLegacy

Compared 19% of the time

webMethods.io vs OpenLegacy

Compared 15% of the time

More OpenLegacy Competitors

Product Reports

Layer7 API Management

Download Layer7 API Management product report

Download OpenLegacy product report

Also Known As

CA API Management, CA Live API Creator, Espresso Logic, CA API Gateway

No data available

Learn More

Broadcom

Overview

Layer7 API Management is a comprehensive solution that enables organizations to securely expose, manage, and monetize their APIs.

It provides features such as API gateway, developer portal, analytics, and security to ensure seamless integration and control over API traffic.

With Layer7 API Management, businesses can streamline their API operations and drive innovation.

OpenLegacy helps organizations quickly launch innovative digital services by extending their core back-end systems to the web, mobile and cloud in days or weeks versus months. Our microservice-enabled API integration and management software quickly reduces project backlog by automating and accelerating microservices and API creation, deployment, testing and management from core applications, mainframes and databases. Together, business and IT teams can quickly, easily and securely meet consumer, partner or employee demands for digital services without modernizing or replacing core systems, and without special programming skills or invasive changes to existing systems and architectures. OpenLegacy is designed for ongoing management of microservices APIs and is based on open standards, so our software plays nice with your current technology stack and supports agile, DevOps and continuous development. Learn why leading companies choose OpenLegacy at www.openlegacy.com.

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...

Layer7 API Management vs. OpenLegacy