What is your primary use case for Apigee?

We are using Apigee in several scenarios across different environments. It serves as our main gateway for APIs, facilitating communication with both external and public entities. This includes complete capabilities like security, implementing various features, high availability, and monetization. Apigee is extensively customized to meet our needs.

Mainly for my previous customer, Apigee was used for API management.

We are implementing Oracle API Platform Cloud Service and using Apigee for enterprise solutions, particularly focusing on minimal technical dependency and integration capabilities suitable for banking and retail domains.

I’m involved in all the R&D work, building solutions, and designing architectural designs that include Apigee and other open-source API managers. As a Google partner, my major focus is on Apigee. Another API manager, WSO2, is open source and suitable for organizations that cannot afford Google Cloud Platform services. However, I mainly use Apigee in my integration, modernization, and architectural designs. I ensure that customers and organizations have an integration layer in their modernization journey and that layer needs an API gateway. The solution provides a complete API management solution and is one of the most important in the industry. It offers three deployment models: cloud-based, on-premises, and hybrid. I have skills and experience in building, installing, configuring, and managing all three deployment models.

We have been using the solution for multiple customers. We performed a greenfield implementation for one of our customers in Canada. It is a complete enterprise platform. The version is Apigee X. We have also created an in-built developer portal. It is mostly used for external APIs, exposing APIs to partners and vendors. One of our banking customers also uses Apigee. They use it more like a gateway and not like a full-fledged marketplace. We are also doing a lot of support work for one of our European customers. They have internal and external API exports on Apigee. We support the whole platform. We have done a lot of automation, built a lot of processes, and brought in governance.

The bank embarked on a journey towards open banking solutions, particularly in the realm of online banking and medical services. This initiative prompted the need for a gateway solution, and after careful consideration, the bank chose Apigee as its API management platform. Since then, the collaboration with Apigee has proven beneficial, leading to ongoing improvements and learning experiences for the teams involved.

Apigee is an API gateway used for API management.

We use Apigee in health care, where multiple databases and applications need API. So far, there has been no standardization, but in the near future, there will be standardization towards the FHIR, which will drive interoperability and integration.

It is mainly used for business applications.

We use the solution as a platform to integrate different APIs and provide authentication, authorization, and performance security services.

We just started with the solution and are learning about its functionality and use cases right now. It's a requirement in our company that we have a tool of this nature.

Our primary use case for Apigee is as an API management tool. Our client has a fast platform and they want to go to the next level when it comes to customization. As they are looking to go beyond minimalistic customization, they need multiple versions of servers and several APIs. This was a challenge we solved with Apigee.

This is our major service when we have services and need an API gateway. They allow us to expose these services to clients.

In my previous company, I used Apigee after modernization to manage client APIs.

We are utilizing Apigee as a means to host and manage our internal APIs. This involves creating an Apigee proxy that acts as a reverse proxy and hosting it on our gateway. When external customers want to use and monetize our internal APIs, we use Apigee to host them. Additionally, for internal applications that require interaction with our existing APIs, we also host them on Apigee.

It's deployed on the cloud. There are a few hundred people in my organization who use this solution.

We want to sell API products and if you want to market the API product that you are building, then definitely you can go for the Apigee or any API product, but if you are in Google Cloud, definitely you can go for Apigee because only Apigee offers current cloud.

We use it for access. for example, if a third-party needs access, they can get it via Apigee.

We use this for intuition with a third party.

We are a telecom-based organization, so our use cases are generally based on telecom functionalities like the MF APIs. I'm a technical architect and we partner with Google.

It is an API gateway. It provides protection to our backend services.

The solution is used for exposing the APIs mainly.

I use Apigee for healthcare management.

Essentially, we have our own product where we have hosted the APIs and Apigee for consumers to consume. We have an airline domain and our own product. We provide services to our clients, who are end users.

We have a legacy and non-legacy databases that are both on-premises and off-premises. Apigee is used to connect to any Google-based applications that are available. In addition, we are experimenting and testing in other environments. I'm a CIO in consulting.

One of our use cases for Apigee was when we were exposing a legacy application that we were using in the past.

I am API architect. We are service providers and provide API solutions to our customers.

We use Apigee an API gateway solution. It can be used in many areas or industries. For example, in Indian, the railway and finance sector, or in Australia, for the Oil Industry.

I use it at home to scan my local drive for malware or viruses.

I'm a part of a service provider company, and we basically provide all kinds of services for our customers. One of the areas for which we provide services is API management. We work a lot with Apigee, and we have experience and a good team working with Apigee. In terms of use cases, we've created a good marketplace for one of the clients. They are a logistics company, and they have a lot of vendors and partners with whom they work. So, we have created a marketplace where the vendor's partners can integrate for their shipments and other things. They can integrate their applications into this marketplace. We have also implemented developer portals where we do the onboarding of developers. They can create their code SDKs, etc. Currently, we are at a customer site, and we are migrating the on-premise version H to Apigee X, which is the latest one.

Apigee is a platform for developing and managing APIs.

We are customers of Apigee.

I'm a developer as well as an architect. We have internal clients as well as external clients. We have other teams within the enterprise that use this platform. They do development, and sometimes, we do development for them. Then we host these solutions in the same infrastructure. We also have external clients who want to integrate their applications with us.

The solution is primarily used for developing and publishing internally IPA (80% of the time). The other 20% of the time the product is used to create and develop an ecosystem with various partners.

The solution is primarily used for managing the interactions between channels, customer experience systems, and other systems.

We use Apigee to share open data for the government. It was a pilot project for one of the government teams who wanted to start the journey of open data.

We are working on some client POC where we have all the workloads deployed on Google Cloud. We wanted a gateway that was more like an API Management tool. We wanted to manage all our APIs centrally in one place. For example, we can route the traffic. We can limit, we can perform throttling, we can have the security checks like the authentication mechanism implemented centrally. We can also have a reverse proxy to our service endpoint.

There are plenty of use cases. My clients were using for internal API management as well as external API management, including subscription models and pre-payment models. Essentially, it was for using internal data and selling external data.

We have an API, which I developed using multiple languages and different applications. We have a lot of applications, and they have their individual APIs. We create a proxy for those applications in Apigee, and we expose those proxies to access those APIs.

We are using Apigee as the API gateway. We also use it for our preparation. We use the API for security and a lot of other tasks. Our customer use cases don't have any legacy systems. We're using Apigee, however, Apigee doesn't provide for a subscribe-publisher capability. It meant Kafka was just to provide the matching capabilities of Apigee. However, mainly we consider this solution as the API gateway and management system.

We implement a set of microservices. We expose different APIs and control and monitor the use of the APIs by using Apigee. We have approximately 15 developers.

My current job is to compare all the different API gateways and to create a report for management. We use this tool primarily to secure our API. We have a set of API from our four businesses and we're trying to apply these APIs to multiple applications. For example, third parties can leverage our APIs built to their own solutions and applications and we build applications on top of these APIs. I make the system available like a mobile app. Primarily the API management for the entire ecosystem of AP that we are building and the DGPS are providing, have varied capabilities across the organization. Apigee also acts as a proxy, everything is done within that. We also leverage the developer portal of Apigee as a main feature, which can be given to outside customers by third parties to build their own applications around our API. One of the standout features of Apigee is the different PolyPhaser functions that we use. For example, we use throttling, encryption/decryption and we also use external AP integration with PV.2 I'm a senior architect and big data engineer and we are customers of Apigee.

We primarily use the solution for all of our security. There are a few use cases for us where we use it to protect API to third parties.

It is a Google cloud solution for API management and analytics.

Primarily we do the Apigee implementations for the customer. We are more like a service company. We sell the product and consult with the clients about their needs. There are options for the API gateways and we look at the client's requirements, their budgeting, and then we deliver and install the new solution.

We've got quite a large technology footprint and I'm looking after the integration of our banking platform with our payment systems.

We are using Apigee as our API gateway.

We are a solution provider and this is one of the products that we implement for our clients. We also it it ourselves. Our use case involves accessing functions on our backend systems through a portal used on mobile devices. The app on the mobile device uses the internet portal, and we have the API as a security layer to pass the functions through to the backend.

We use Apigee every day. Because we have a backend system, we use Apigee to capture and track all of our transactions and for monitoring calls, which is the target for our client service. We then use this information to create a report and provide a price for each transaction. For this reason, we created a proxy that we use as an integration layer, like API management, which helps build applications. For that reason, each and every call goes through Apigee so that we can track and capture all of the information.

We are a solution provider and Apigee is one of the API management products that we implement for our customers. Most of our clients want to expose their APIs to their consumers and they need to have a generic infrastructure for it. At the same time, they want it to be scalable as well as highly secure.

The primary use case for this solution is to integrate both external applications as well as internal applications. We use some to integrate other applications, but most of them are just proxies that are for fronting the backend APIs.

We primarily use the solution as API Management, as both proxy and security.

This solution provides us with a good gateway for API Management and versioning. It gives us easy to map backend version services, and additional security and policies can be adopted.

API gateway tool and management of API solutions. This tool is extremely helpful for discovery, self-service of API solutions.

We use this product for exposing API's to the digital platform and for B2B.

We use it to build API proxies for securing targeted back-ends with an emphasis on Continuous Integration/Continuous Development (CI/CD).

It is a platform for the publication of API services, access control, limiting the use of resources, and monitoring consumption.