The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.7.0-M1. It is now available to download. Download
https://github.com/wso2/product-microgateway/releases/download/v2.7.0-m1/wso2am-micro-gw-2.7.0-m1.zip Documentation https://docs.wso2.com/display/MG270/ Introduction 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. Architecture The following diagram illustrates an overview of how API Manager Microgateway works. [image: Architecture] <https://user-images.githubusercontent.com/13759167/46869054-2c3d9280-ce48-11e8-8228-139f9dfa16ca.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 responsibilities. - 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 2.7.0-M1 GitHub (Product-Microgateway <https://github.com/wso2/product-microgateway/milestone/13?closed=1>) Known Issues All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location: GitHub (Product-Microgateway <https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+is%3Aopen> ) How You Can Contribute Mailing Lists Join our mailing list and correspond with the developers directly. Developer List: [email protected] User List: [email protected] 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 <https://github.com/wso2/product-microgateway/issues>). *--WSO2 API Manager Team--*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
