wso2/wso2micro-gw repository overview

⁠Supported tags and respective Dockerfile links

• 3.0.2 (Dockerfile)⁠
• 3.1.0 (Dockerfile)⁠
• 3.1.0-ubuntu (Dockerfile)⁠
• 3.2.0 (Dockerfile)⁠
• 3.2.0-ubuntu (Dockerfile)⁠
• 3.2.1 (Dockerfile)⁠
• 3.2.1-ubuntu (Dockerfile)⁠
• 3.2.3 (Dockerfile)⁠
• 3.2.3-ubuntu (Dockerfile)⁠
• 3.2.4 (Dockerfile)⁠
• 3.2.4-ubuntu (Dockerfile)⁠

⁠Quick reference

• Where to get help:
  Docker Community Forums⁠, Community Slack⁠, Stack Overflow⁠ or mail to WSO2 Developer mailing list⁠

• Where to file issues:
  Product specific issues at WSO2 API Microgateway repository⁠ Docker resource specific issues at Docker resource repository⁠

• Maintained by:
  WSO2 Inc.⁠

• Supported Docker versions:
  Docker v17.09.0 or above

⁠About WSO2 API MicroGateway

The WSO2 API Microgateway is a lightweight, gateway distribution which can be used to expose single or multiple APIs.

In summary, the WSO2 API Microgateway is a specialized form of the WSO2 API Gateway with characteristics below:

1. Able to execute in isolation without mandatory connections to other components (Secure Token Service, Rate limiting component , Analytics).
2. Capable of exposing micro services directly from Open API definitions
3. Able to host a subset of APIs of choice (defined on the WSO2 API Manager's API Publisher) instead of all.
4. Immutable. The gateway runtime is immutable. If APIs or Policies change after the WSO2 API Microgateway has been built, a rebuild process is required to capture the changes.
5. Seamless integration with deployment automation tools and techniques.
6. Easy integration with CI/CD processes.

WSO2 API Microgateway acts as a proxy that is capable of performing security validations (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.

⁠How to use this image.

Microgateway docker image should be used as the base image for Microgateway runtime images, which can be built using WSO2 API Microgateway toolkit⁠. Refer Quick Start Guide⁠.

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these are likely to contain other software which may be under other licenses (such as Bash, etc. from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.