Our company exposes different APIs, and we use it to monitor traffic, limit traffic, and similar functions.

I don't have much involvement with the solution, though I did conduct some research.

We set up endpoints as a service provider on the server side, not on the consumer side.

We have a microservices architecture or our public API managed through the 3scale.

This use case was for one of our Gulf clients, specifically in the ranking domain.

3scale API Management is used for routing the internal application within the company.

We use the solution for external service communications.

We use 3scale to manage, monitor, and secure APIs and back up endpoints. 

I mainly use 3scale API Management as an API management tool.

The use case is that the organization I work for wanted to work with APIs but they didn't actually know what to do. They knew that it was a good thing to have an API management product. We are now trying to establish an API-first approach for both internal and external APIs, and we use it to provide financial information via APIs.

The deployment is a hybrid. We deploy the gateways in our own OpenShift cluster, provided by a vendor, but not on the cloud. And we have the RHOAM (Red Hat OpenShift API Management) solution for the management part, and that runs on AWS.

We are a solution provider and this is one of the products that we implement for our clients.

This is a container platform with a developer portal.

3scale: what a really good product to secure an unsecure API if you have multiple backend unsecured routes provided by an ESB (Red Hat Fuse), and available through one unique frontend acting as a secure gateway (with HTTPS protocol and API keys).

Our primary use for 3scale is for promising internal and external exacts, as well as providing HIT to computers.