The API Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are:
- The ability to execute in isolation without mandatory connections to other components (Key Manager, Traffic Manager, etc).
- The ability to host only a subset of specific APIs (defined in the API Publisher), instead of all.
- Immutability; if you update an API, you need to re-create the container/instance and hot deployment is not possible.
Microgateway offers you a proxy that is capable of performing security validations (OAuth, Signed JWT), in-memory (local) rate limiting and operational analytics.
The following topics explain further details about the API Microgateway, its architecture and capabilities, and how to configure, deploy and troubleshoot it:
- Overview of the Microgateway
- Microgateway Quick Start
- Grouping APIs with Labels
- Overriding Endpoint Information
- Importing Certificates to the API Microgateway Truststore
- Analytics for Microgateway
- Deploying the API Microgateway in Docker
- Deploying the API Microgateway in Kubernetes
- Working with the Microgateway in a Windows Environment
- Troubleshooting the Microgateway
- Microgateway Configurations