[prev in list] [next in list] [prev in thread] [next in thread]
List: esb-java-dev
Subject: [Dev] WSO2 API Microgateway 3.0.0-Beta Released
From: Praminda Jayawardana <praminda () wso2 ! com>
Date: 2019-04-29 20:42:00
Message-ID: CAAVsST4xK4mfTWkR5mNcs7tbR2QG34J6KBUaKHx+=4Rt3rb_2w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
The WSO2 API Manager team is pleased to announce the release of WSO2 API
Microgateway 3.0.0-Beta. It is now available to download.
Download
https://github.com/wso2/product-microgateway/releases/download/v3.0.0-beta/wso2am-micro-gw-3.0.0-beta.zip
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.
[image: Architecture]
<https://raw.githubusercontent.com/wso2/product-microgateway/dev_first/architecture-new.png>
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-Beta
GitHub Fixed Issues
<https://github.com/wso2/product-microgateway/milestone/18?closed=1>
Known Issues
All the open issues pertaining to WSO2 API Microgateway are reported at the
following location:
GitHub Open Issues
<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: 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 <https://github.com/wso2/product-microgateway/issues>
).
*--WSO2 API Manager Team--*
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail-m_-8720955638927959535m_-9117414683511899942m_-6472670576465913445gmail-comment-body \
gmail-m_-8720955638927959535m_-9117414683511899942m_-6472670576465913445gmail-markdown-body \
gmail-m_-8720955638927959535m_-9117414683511899942m_-6472670576465913445gmail-js-preview-body" \
style="min-height:682px"><h2>The WSO2 API Manager team is pleased to announce the \
release of WSO2 API Microgateway 3.0.0-Beta. It is now available to download.</h2>
<div><h3>Download</h3>
<p><a href="https://github.com/wso2/product-microgateway/releases/download/v3.0.0-beta/wso2am-micro-gw-3.0.0-beta.zip" \
target="_blank">https://github.com/wso2/product-microgateway/releases/download/v3.0.0-beta/wso2am-micro-gw-3.0.0-beta.zip</a></p></div><h3>Documentation</h3>
<p><a href="https://docs.wso2.com/display/MG300/" rel="nofollow" \
target="_blank">https://docs.wso2.com/display/MG300/</a></p> <h3>Introduction</h3>
<p>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.</p>
<p>In summary, a Microgateway is a specialized form of the WSO2 API Gateway with \
characteristics below:</p> <ol><li>Its ability to execute in isolation without \
mandatory connections to other components (Secure Token Service, Rate limiting \
component , Analytics).</li><li>Expose micro services directly from Open API \
definitions</li><li>Ability to host a subset of APIs of choice (defined on the WSO2 \
API Manager's API Publisher) instead of all.</li><li>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.</li><li>Seamless \
integration with deployment automation tools and techniques.</li><li>Easy integration \
with CI/CD processes.</li></ol> <p>Microgateway offers you a proxy that is capable of \
performing security validations (Signed JWT, OAuth), in-memory (local) rate
limiting and Analytics.</p>
<h3>Architecture</h3>
<p>The following diagram illustrates an overview of how API Microgateway works.</p>
<p><a rel="noopener noreferrer" \
href="https://raw.githubusercontent.com/wso2/product-microgateway/dev_first/architecture-new.png" \
target="_blank"><img \
src="https://raw.githubusercontent.com/wso2/product-microgateway/dev_first/architecture-new.png" \
alt="Architecture" style="max-width: 100%;" class="gmail-CToWUd"></a></p> <h3>Setting \
up Microgateway</h3> <p>This product will include a CLI, the B7a platform \
distribution and a few B7a extensions (Endpoints and Filters). Running Microgateway \
has two main steps.</p>
<ul><li>Setting up a Microgateway project.</li><li>Running the Microgateway \
project.</li></ul> <p>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.</p>
<h3>Bug Fixes And Improvements in 3.0.0-Beta</h3>
<p>GitHub <a href="https://github.com/wso2/product-microgateway/milestone/18?closed=1" \
target="_blank">Fixed Issues</a></p> <h3>Known Issues</h3>
<p>All the open issues pertaining to WSO2 API Microgateway are reported at the \
following location:</p> <p>GitHub <a \
href="https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+is%3Aopen" \
target="_blank">Open Issues</a></p> <h3>How You Can Contribute</h3>
<h4>Mailing Lists</h4>
<p>Join our mailing list and correspond with the developers directly.</p>
<p>Developer List: <a href="mailto:dev@wso2.org" target="_blank">dev@wso2.org</a></p>
<h4>Reporting Issues</h4>
<p>We encourage you to report issues, documentation faults, and feature
requests regarding WSO2 API Microgateway through the public (<a \
href="https://github.com/wso2/product-microgateway/issues" target="_blank">API \
Microgateway Git Repo</a>).</p> <p><b>--WSO2 API Manager Team--</b></p></div></div>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic