[Announce] WSO2 API Manager Microgateway 3.0.0-M1 Released

Rukshan Premathunga rukshan at wso2.com
Fri Oct 12 04:42:30 PDT 2018

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

- [wso2am-micro-gw-3.0.0-m1.zip](


The API Manager Microgateway provides the capability to create specialized
gateway distributions (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 by
having below main characteristics:

   - Its ability to execute in isolation without mandatory connections to
   other components (Key Manager, Traffic Manager, etc).
   - Ability to host a subset of APIs of choice (defined on the API Publisher)
   instead of all.
   - Immutability - if you update an API you need to re-create the
   container/instance, no hot deployment.

Microgateway offers you a proxy that is capable of performing security
validations (OAuth, Basic Auth, Signed JWT), in-memory (local) rate
limiting and operational analytics.
Design Goals

Following are some of the main expectations of Microgateway

   - Ability to host just one or a selected set (subset) of APIs only.
   - Ability to execute in complete isolation once setup, without having
   the need to contact the Management or Security components.
   - Easy integration with CI/CD processes.
   - Seamless integration with deployment automation tools and techniques.


The following diagram illustrates an overview of how API Manager
Microgateway works.
[image: image.png]
Setting up Microgateway

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

   - 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. For example, what gets run as default on a
Microgateway is a simple API proxy. If a developer needs to perform some
sort of an integration or change the Ballerina source files for some other
reason, he could engage with the project after the setup phase and do the
required modifications before the distribution is built.
Bug Fixes And Improvements in 3.0.0-m1

   - GitHub (Product-Microgateway

Known Issues

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

   - GitHub (Product-Microgateway

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.


   Developer List: dev at wso2.org | Subscribe | Mail Archive

   User List: user at wso2.org | Subscribe | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults, and feature
requests regarding WSO2 API Manager Microgateway through the public API
Manager Microgateway Git Repo
-- The WSO2 API Manager Team --

Rukshan Chathuranga.
WSO2, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/announce/attachments/20181012/be34c52d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 219802 bytes
Desc: not available
URL: <http://mail.wso2.org/pipermail/announce/attachments/20181012/be34c52d/attachment-0001.png>

More information about the Announce mailing list