I have some suggestions which I think are important to implement. 1. It looks like there's a lot of information being duplicated in the open API file and the definitions.yaml. 2. A user needs to enter at least 6 fields to the definitions.yaml to create a very basic API. This is a tad too much IMO. 3. When defining resource based endpoints and functions a user needs to copy paste data from the open api file, which I think creates a sense of redundancy. 4. Given the reasons above it would be best to introduce vendor extensions to the open API file to capture the additional information we require. 5. The distribution size has increased to 224MB. I think we should host the runtime and design time separately. Basically a gateway.zip and gateway-sdk.zip. We should create a mode where we can run the compiled source on the binary. Ex: gateway.sh --dir=/home/projects/foo/target.
On Tue, Apr 30, 2019 at 2:01 AM Praminda Jayawardana <prami...@wso2.com> wrote: > 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: d...@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--* > -- *Nuwan Dias* | Director | WSO2 Inc. (m) +94 777 775 729 | (e) nuw...@wso2.com [image: Signature.jpg]
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
