The Microgateway's responsibility is focused on a single micro-service or a small number of micro-services. To manage a micro-service landscape an API Gateway is required. It offers the user interface for configuring the policy configuration and system configurations. Moreover, it is responsible for monitoring the traffic within the micro-service landscape. The following figure shows how Microgateways are interacting with an API Gateway.

The Microgateways pull the assets including APIs, applications, and policies from the API Gateway where they are configured. Also, other administrative settings including SSL configuration and fault configurations are defined in the API Gateway and pulled by the Microgateway during startup. The download of assets is done through the API Gateway REST APIs.

While monitoring the API requests and responses, the Microgateway pushes the runtime analytics information to API Gateway. API Gateway provides a consolidated view through its dashboards.

The download of assets and administrative settings can be done up-front using the Microgateway tooling that allows to provision stand-alone Microgateways, which do not require any connection to a running API Gateway. Stand-alone Microgateways do not allow to perform a consolidated traffic monitoring of a micro-service landscape.