The solution secures your API/Service/Application in a matter of minutes. It also provides the capability for translating services from one format to another (SOAP to REST, REST to SOAP, GraphQL - API, and vice versa). Broadcom API Gateway would provide you 1000+ out-of-the-box assertions and certain custom assertions to meet your development and integration requirements. Rather than building an application in hours through coding the Drag and Drop capability, allows you to create APIs in minutes. The runtime setup allows coding and testing at a faster pace without the need to deploy and redeploy applications for every version build published. Failure if any the code could be rolled back in a matter of seconds and activated. So it provides a good framework that is tried and tested over the years and provided a Robust OOB Security and Implementation interfaces.

I use the solution since I work for many different kinds of domains and different kinds of organizations, including the banking and financial sectors.

We use this solution for security as well as for monetization. I'm a certified CA API management professional and a user of this solution. We are vendors of Layer7.

I am an Enterprise API architect and we are one of the biggest conglomerate organizations in Dubai. We have a lot of retail businesses,  automotive businesses, and other interests. What we are doing is using the API Management to build out a proper, consistent API layer for our legacy systems and microservices as well. That will enable us to expand our reach in digital channels. This will also help us serve the API Products for 3rd part consumptions.

We are already using Dell Boomi in our organization for ESB purposes and are more focused on that development right now and hope to do more with Layer7 in the future.  

I used the solution in my company since I was involved in the designing of the network and security. Right now, I am designing all the solutions in our company's environment.

My company faced a ransomware attack in 2022, after which we installed a honeypot to deal with DDoS attacks. Layer7 API Management was implemented to deal with ransomware attacks since they compromise our company's security.

The primary use case for Layer7 API Management is patient services, such as patient care and health care services, where patients would like to check appointment details and reports on mobile applications.

Another use case for the product is sharing the data with external organizations related to healthcare.

Layer 7 API management is my go-to solution for handling the entire API lifecycle. From governance and management to developer onboarding, monitoring, and analytics, it simplifies and secures the process.

We have one Global customer using Layer7 API Management for their entire API management. They have exposed APIs to their external partners and vendors through a marketplace. However, Layer7 API Management is primarily used as a gateway solution, and its management capabilities are not as strong as those of other solutions available. As a result, the customer also uses Apigee for API management tasks. Apigee has been used throughout the customer's API program, including building the marketplace, monetizing APIs, and developing a developer portal.

It serves our development purposes, enabling the connection of both external and internal clients, for example.

We have more than 50 applications in the backend. We monitor the infrastructure through a database monitoring tool. Our daily tasks involve working on P1 incidents, managing change requests, conducting patching updates, working on P2 tickets, backend server certificate renewals, etc. 

We use a combination of Denodo and Layer7 API Management. The APIs are developed on Layer7 and then exported through Denodo. Layer7 provides the security layer, while Denodo facilitates data on demand. That combination is handy, and most organizations have a similar setup. That data is exported to API. The data modeling is done on Denodo and exposed through policies developed on Layer7 API Management.

It's good to have a tool for integrating data between organizations and applications. The combination of Denodo and Layer7 is beneficial. I feel like Layer7 would not be sufficient because most APIs need data on demand. We need to provide data on demand on top of some layers without going back into the native data systems. 

That will help developers not tax something on the line. We just develop on top of those databases or data layers. You prepare a logical data layer to provide an API exposed through Layer7. Using Layer7 and Teams or different applications can consume those data easily. 

We use CA API Management for our brand mobile app and our outbound traffic. Our brand mobile apps are for Olive Garden, Capital Grill and LongHorn Steak House.

We also use API Management to modernize legacy systems via microservices.

We have our internet application, which is connected to PeopleSoft and other tools so we can export through API gateway. So we have a custom mobile app built for our internal application, where people can check their paychecks, benefits, and other perks, such as gift cards.

Layer7 API Management can be deployed on the cloud and on-premise.

We are using Layer7 API Management to expose APIs and to do security checks, which is similar to a reverse proxy.

We use the product for HTTP traffic. It supports DNS and FDP protocols. 

We started off exposing REST APIs to other business units and our external partners by doing legacy integration.

The Gateway is a security control point and a way to drive standardisation.

Live API Creator is used very successfully by one of our businesses to run all their APIs. Other BUs use the Live API Creator to create the easy, "quick win" APIs, which do not make sense to host on the ESB or where resources are not available to do it quickly.

We handle some SOAP services where we are only interested in adding additional security and metrics on top of the SOAP services. We even transform JSON REST to SOAP where legacy internal ESB systems are not able to use REST.

We have seen a huge uptake in routing messaging services, like SMS and WhatsApp. The Gateway currently serves to standardise these into a single API view with multiple channels.

We use it as a gateway for protecting some of our critical infrastructure out on the grid. We have six data centers and it is implemented in each one of them, protecting our grid.

We have several applications that talk to the grid, and they pass through that gateway to get out there, ensuring that we terminate connections from the lower security environment and reestablish credentials for the higher security environment.

It is primarily used for API Security. It has performed very well on the basic security front, but then this product is a suite of products, so it has multiples of products. We are not using all of the subproducts. Now, we are looking for a new use case where we want to use it for mobile apps. That is what we are currently exploring.

Our clients use the solution for a secured layer to protect their API. Most of them have two kinds of API, the frontend, and backend.

Our primary use case for this solution is opening up our APIs to the development community so they can help us innovate some of our banking products. We've demoed CA API Management and we've done one proof of concept with it, but we are not using it on an ongoing basis.

API management, for security.

API gateway.

We are using Layer7 API Management as an enterprise service bus, ESB, and B2B security gateway.

We primarily use Layer7 API Management to monitor stuff. I'm the one who installs it. They sent me a TAR file, I unloaded it to TAR, brought it up, and made everything work. I gave it the three different network configurations to talk to the three different domains, and then I turn it over to the guys, and they do what they got to do with it.

My company is a CA partner. We do implementations for end-customers, using CA API Management. So my company doesn't use the product, but we install, configure, and implement the product for our end-customers.

Primary use for the solution is to have access to APIs that are generally difficult and not available. An example would be critical APIs that should be available 24/7 but they are not available most of the time, because of one or another constraint. That is where the API Management solution is used to the maximum by end-customers.

Our primary use case is as an API gateway for authentication and authorization, and then lightweight transformation or lightweight mediation. But it's mostly, authentication and authorization, mostly security-based.

Mainly for our API gateway. We use it for onboarding APIs and then getting those internally. We have them through the B-to-B channel, we have them through a member channel, and then internally as well, to service our APIs.

It has performed pretty well. We've had an issued with scaling, internally, when we slammed it one time with a very, very high rate of transactions; we're talking like 65 million an hour. Whenever we did that we weren't ready for it yet, so we had to back out, but it's been good.

We have many use cases. We are doing an enterprise install for all CA API management tool searches which are covered under the ELA, Enterprise License Agreement. We have close to a 100 plus use cases that we want to deploy, the next is over a six months to one year timeline.

I have used this tool for my customers, as I am a service provider, not an end user. I have dealt with implementations and configurations for CA API Management.

We implemented the API versioning for software services and REST services.

I use CA Live API Creator to integrate data from a variety of sources, and then to provide an API response to calls from my client applications.

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.

The primary use case is we are using the API Management Suite. It has the Gateway and Portal, and we are using the Gateway to front all the APIs in FedEx.

The Gateway is performing very well. The Portal is not.

Our primary use case is for API management. We use it as a security gateway in our DMZ and ESB and our trusted zone.

It works great. We haven't had any problems, it just runs.

We use the API Gateway as a front door to access our APIs that we host internally, to enable us to get involved in the digitalization.

It has performed very well, actually. It's given us new capabilities that we never had before and gives us more confidence in increasing the number of APIs that we actually have.

We use Layer7 API Management to manage API gateway and customize policy scripts.

Our primary use case is basic encryption/decryption using symmetric assertions and then, gradually, SOAP signatures, SOAP encryption, non-SOAP XML encryption, and signing that. In the last six months or so, I have been working on JWT (JSON Web Tokens).

Primary user case is producing APIs as products, essentially, and creating the environment for developers to sign up to use APIs. 

It has performed well so far. We just got a test instance installed, and did a PoC earlier in the year. We are more or less just getting started with it. 

We use it for security.

So far so good. We have our own challenges - some monitoring and some performance related things - but at the same time, I think it's pretty good.

We've been using it to program intermittently. There's a problem with one version, which saves pretty slowly. Now it's good. Then we found that this is cheaper. The advantages include the coding, as well as getting emails and alerts from them.

We use Layer7 API Management for digital banking: for signing, validation, transactions, etc.

We are a partner, so there are roughly 40 people inside my company working with Layer7.

We are using it for controlling all web services, traffic, or API traffic. All connections are going through the Layer7 API gateway. That is done for the purpose of security, management, and governance.  

I sell this solution to a variety of clients in digital banking, insurance, and health care.

RESTful API implementation and exposure.

We use it for public API security.

We use this as a Cyber security appliance and also as a centralised API management platform for partners.

This product is used to expose some internal APIs to help us automate different activities.

We have the API Gateway deployed in production. The primary use case is for the API Gateway to provide API access, and authentication, and authorization for the APIs we expose through our product. 

I am also looking forward to having the API developer portal deploy as well so we get a bit more insights into the analytics part, and also some of the API lifecycle management associated with it.

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.

Our primary use case is to enable our customers who are on the Internet. We want them to access our protective web series behind a corporate firewall. To do that, we like to use the OAuth ToolKit within the CA API. It can minimize the password exposure by generating a token using the ToolKit, then use the token to make the web services calls to our protected back-end services.

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

API security, API management, OAuth security, microservices, mobile app security.

Web services authentication. 

So far so good, in terms of performance.

We had a test version, which was more of an on-prem version, and we also had some on the Docker for a live API creator. 

We are a security service company, and we provide a lot of solutions in that space. We were just trying to have a frictionless authentication product, so we were working on that. We were looking for a Gateway that can serve in an API, and we've already got an open-source solution.

We use CA API Management to publish APIs for secure and fast integration with customers and partners.

To protect the web services, security, authentication; protect against any kind of attacks from external sites.

We have been using API Gateway for four years and we have huge class actions, like 600 parts per second, and we have not seen any issues as of now. It's stable.

The primary use case would be services for APIs that we are going to expose either internally, within the enterprise, or at the outside edge of the enterprise.

Previously, we don't have a security for our web or mobile applications. In a scenario where I have an application that gives APIs to everyone in the world, they can directly access that particular application. However, this allows for different types of attacks on that particular application too. This becomes a problem if a number of users access it, whether they are valid or invalid users, they will see performance issues. If a number of attacks are happening on a particular application, it goes down. So, from a security perspective, CA API Management acts like a reserve proxy.

It makes the end user feel like it is a real system. It does not show the back-end and what the API tool does. CA API management will not let people know that there is an original server running behind the tool. That is the security point of it. 

For use cases, there are databases that some people have to query on. With the help of CA API Management tool, we can give APIs to the end user, and with the help of those APIs, they can access the data instead of the database.

• Digitalization
• API Life Cycle Management

CA API Management powers the next generation of mobile and Internet of Things (IoT) applications by providing reliable connectivity between data, people, apps and devices. You can aggregate and orchestrate data from multiple data sources into modern REST APIs almost instantly. Whether your data is in legacy systems, disparate databases, or the cloud, you will be able to bring it all together to power new digital initiatives at scale in modern apps or SaaS applications.

We use it primary for API management in my data center, for mobile applications and application-to-application integration.

Our primary use case is to host a handful of different API services for the consumers of our customer. We build and maintain several of those APIs right on the Gateway using their policies. We use it to kind of proxy request through to Java services and other things that we have created.

Administration and configuration of the platform API management version 9.2. SaaS, security configuration, design, and implementation of APIs, which are exposed to partners of the company for the execution of business flows. All this is done quickly and easily with minimal effort.

Security. We have a lot of APIs, a lot of web services inside Motorola, and we wanted to have a solution which can secure all our APIs.

So far it has been doing well. But we are looking towards microservices technology. And we heard here, at this CA World conference, that they are coming up with a microservices API gateway. That is something that we would be interested in looking into. 

But as far as far as the classic API gateway goes, I think it is definitely doing well. We were bought by Lenovo, and eventually Lenovo, which did not have this solution, has also been convinced to use it. So overall, as one company, both Lenovo and Mortola will be using this product.

API security and API onboarding. We have on-premise deployment with legacy backends.

We have a full, classic, API gateway currently. We want to leverage it to use the microservices, with the help of micro API gateway, to support our business or e-commerce platform, the API traffic. That's our main our goal, to move further toward a microservice with a Docker container.

We implemented it in a non-prod and it is good. But we want to move into production going forward. Performance-wise it’s good, and we are not seeing any issues.

In my company, we use CA API Management for banks in the financial markets. Our primary use case is for the basic protection of the APIs. We also use the authentication feature.

Managing all of our APIs and the security around them.