Skip to content

WSO2 API Microgateway 3.0.0-Beta2 Released!

Pre-release
Pre-release
Compare
Choose a tag to compare
@praminda praminda released this 13 May 13:07
· 1615 commits to master since this release
v3.0.0-beta2
2d5c06b

The WSO2 API Manager team is pleased to announce the release of WSO2 API Microgateway 3.0.0-Beta2. It is now available to download.

Documentation

https://docs.wso2.com/display/MG300/

Introduction

The Microgateway provides the capability to create specialized gateway distribution (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.

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

  1. Its ability to execute in isolation without mandatory connections to other components (Secure Token Service, Rate limiting component , Analytics).
  2. Expose micro services directly from Open API definitions
  3. Ability to host a subset of APIs of choice (defined on the WSO2 API Manager's API Publisher) instead of all.
  4. Immutability - The gateway runtime is immutable. If APIs or Policies change after the 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.

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

Architecture

The following diagram illustrates an overview of how API Microgateway works.

Architecture

Setting up Microgateway

This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). Running Microgateway has two main steps.

  • Setting up a Microgateway project.
  • Running the Microgateway project.

These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required.

Bug Fixes And Improvements in 3.0.0-Beta2

GitHub Fixed Issues

Known Issues

All the open issues pertaining to WSO2 API Microgateway are reported at the following location:

GitHub Open Issues

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer List: dev@wso2.org

Reporting Issues

We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the public (API Microgateway Git Repo).

--WSO2 API Manager Team--

Assets 6
Loading