The new microgateway-coresident plan leverages the meta buildpack through which the API runtime (the Apigee Microgateway) can be injected into the app container as a sidecar proxy using config/build constructs. Apigee Microgateway’s light footprint deployment model makes it easy to co-reside within apps/microservices developed in CF. Generally the coresident model provides the following benefits and features: - A lack of routing overhead, as Apigee Microgateway is embedded into the app container, making this option great for apps that have low latency requirements. - Automatic scaling, as Apigee Microgateway is part of the app container, so it participates in the app lifecycle process and scales up automatically as the app is scaled. - Consistent and pervasive protection to service implementations, as all ingress to the service runs through Apigee Microgateway. - Analytics across API exposures, as Apigee Microgateway provides a lightweight mechanism for capturing analytics for all use cases. - Consistent access to APIs by leveraging common infrastructure for API keys, tokens, and API product definitions. - A single, self-service developer portal for internal and external API consumers. http://docs.pivotal.io/partners/apigee/proxying-microgateway-coresident.html This video walks you through the "microgateway-coresident" plan can be used to provide API Management for your microservices.