Apigee Edge Microgateway
Note: Description and code apply to Microgateway v2.x It's not compatible with v1.x series of Microgateway.
The Apigee Microgateway is a lightweight API management proxy that routes requests and responses between API consumers and API providers. As requests are routed the microgateway introduces an eventing model that is based on the concept of http middleware. You can add custom plugins to the http router via the plugins directory. You can also change the code to explicitly load plugins via the gateway.addPlugin method. For more information about plugins see https://github.com/apigee/microgateway-plugins. For more information on how to use the producet see the product documentation
The Microgateway is composed of 3 components
It also provides a CLI that an admin uses to wire/configure an instance of Microgateway with their Edge (Cloud or On-Premises) org as well as start Microgateway. Below is the workflow of the cli. In order to load custom plugins you must load your plugin in the plugins directory. The plugins directory is configured in the default.yaml or in the specified config directory.
The official docs for Microgateway can be found on the Apigee website.
The Apigee community is the best place to ask questions, suggest features, and learn best practices with Microgateway.
For filing issues please follow the following steps, and file the issue here.
Pull requests to microgateway repos are gladly accepted. However, to make it easier on maintainers reviewing requests we kindly ask that you include the following with each pull request.