Deploying Microgateway in Docker and PaaS
How to add API management capabilities natively on the microservices stack of your choice
A lot of enterprises are exploring microservices as an architecture pattern for building or exposing new APIs. Often, a microservices strategy includes an infrastructure stack with components like Docker, Cloud Foundry, Kubernetes, and OpenShift, or cloud-native PaaS platforms like Google App Engine (GAE) and Azure App Services. Apigee Edge provides API management capabilities for microservices deployed in such an infrastructure stack.
In this post, we’ll explain the power of Apigee Edge Microgateway and the options for deploying it. In an upcoming installment, we’ll walk you through a handful of quick tutorials to get you started deploying Microgateway as a Docker container, in PaaS platforms like Cloud Foundry, and in GAE and Azure App Services.
These options help microservices developers and teams add API management capabilities natively on the microservices stack of their choice.
What is Apigee Microgateway?What is Apigee Edge Microgateway, you ask? It’s a secure, HTTP-based message processor for APIs. Its main job is to process requests and responses to and from backend services securely while asynchronously pushing API execution data to the Apigee Edge API platform, where it’s consumed by the Edge analytics system.
Edge Microgateway is easy to install and deploy—you can have an instance up and running within minutes.
Typically, Edge Microgateway is installed within a trusted network, in close proximity to backend target services. It provides enterprise-grade security, and some key plug-in features including spike arrest, quota, analytics, and customer extensions, but not the full capabilities or footprint of Apigee Edge. You can install Edge Microgateway in the same data center or even on the same machine as your backend services.
The power of hybrid API managementMicrogateway provides the user the ability to perform hybrid API management, which enables a user to:
- Centrally define/author API proxies
- Centrally define API products, developer apps, and developer catalogs, among other things
- Distribute policy enforcement of API proxies on many gateways, which can be deployed on customer data centers or other cloud providers
- Centrally collect and view API analytics