Bot releases are hidden (Show)
Published by Rajith90 almost 5 years ago
Bug Fixes And Improvements in 3.0.3
Known Issues
Try it
https://github.com/wso2/product-microgateway#microgateway-quick-start
Documentation
https://docs.wso2.com/display/MG300/
How You Can Contribute
-
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues. -
Contributing Code
Read through project Contribution Guidelines to learn how to contribute with code. -
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda about 5 years ago
Bug Fixes And Improvements in 3.0.2
Known Issues
Try it
https://github.com/wso2/product-microgateway#microgateway-quick-start
Documentation
https://docs.wso2.com/display/MG300/
How You Can Contribute
-
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues. -
Contributing Code
Read through project Contribution Guidelines to learn how to contribute with code. -
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
Bug Fixes And Improvements in 3.0.1
Known Issues
Try it
https://github.com/wso2/product-microgateway#microgateway-quick-start
Documentation
https://docs.wso2.com/display/MG301/
How You Can Contribute
-
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues. -
Contributing Code
Read through project Contribution Guidelines to learn how to contribute with code. -
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
Bug Fixes And Improvements in 3.0.1-RC3
Known Issues
Try it
https://github.com/wso2/product-microgateway#microgateway-quick-start
Documentation
https://docs.wso2.com/display/MG301/
How You Can Contribute
-
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues. -
Contributing Code
Read through project Contribution Guidelines to learn how to contribute with code. -
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
Bug Fixes And Improvements in 3.0.1-RC2
Known Issues
Try it
https://github.com/wso2/product-microgateway#microgateway-quick-start
Documentation
https://docs.wso2.com/display/MG301/
How You Can Contribute
-
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues. -
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
Bug Fixes And Improvements in 3.0.1-RC1
Known Issues
Try it
https://github.com/wso2/product-microgateway#microgateway-quick-start
Documentation
https://docs.wso2.com/display/MG301/
How You Can Contribute
-
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues. -
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
Bug Fixes And Improvements in 3.0.0-RC1
Known Issues
Try it
https://github.com/wso2/product-microgateway#micro-gateway-quick-start
Documentation
https://docs.wso2.com/display/MG300/
How You Can Contribute
-
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues. -
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
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:
- Its ability to execute in isolation without mandatory connections to other components (Secure Token Service, Rate limiting component , Analytics).
- Expose micro services directly from Open API definitions
- Ability to host a subset of APIs of choice (defined on the WSO2 API Manager's API Publisher) instead of all.
- 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.
- Seamless integration with deployment automation tools and techniques.
- 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.
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: [email protected]
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--
Published by praminda over 5 years ago
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.
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:
- Its ability to execute in isolation without mandatory connections to other components (Secure Token Service, Rate limiting component , Analytics).
- Expose micro services directly from Open API definitions
- Ability to host a subset of APIs of choice (defined on the WSO2 API Manager's API Publisher) instead of all.
- 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.
- Seamless integration with deployment automation tools and techniques.
- 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.
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
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: [email protected]
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--
Published by praminda over 5 years ago
The WSO2 API Manager team is pleased to announce the release of WSO2 API Microgateway 3.0.0-Alpha. 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:
- Its ability to execute in isolation without mandatory connections to other components (Secure Token Service, Rate limiting component , Analytics).
- Expose micro services directly from Open API definitions
- Ability to host a subset of APIs of choice (defined on the WSO2 API Manager's API Publisher) instead of all.
- 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.
- Seamless integration with deployment automation tools and techniques.
- 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 Manager Microgateway works.
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-Alpha
GitHub Fixed Issues
Known Issues
All the open issues pertaining to WSO2 API Manager 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: [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).
--WSO2 API Manager Team--
Published by praminda over 5 years ago
The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.7.0-M2. It is now available to download.
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.
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-M2
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 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).
--WSO2 API Manager Team--
Published by praminda over 5 years ago
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.
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.
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)
Known Issues
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
GitHub (Product-Microgateway)
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).
--WSO2 API Manager Team--
Published by fazlan-nazeem over 5 years ago
The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0. It is now available to download.
Download
https://wso2.com/api-management/api-microgateway/
Documentation
https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway
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.
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.6.0
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 Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
Developer List: [email protected] | Subscribe | Mail Archive
User List: [email protected] | 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).
Published by Rajith90 about 6 years ago
The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 3.0.0-M2. It is now available to download.
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 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)
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.
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 3.0.0-m2
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 Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
Developer List: [email protected] | Subscribe | Mail Archive
User List: [email protected] | 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).
Published by Rajith90 about 6 years ago
The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 3.0.0-M1.
Introduction
The API Manager 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 by having below main characteristics:
- 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.
Documentation
https://docs.wso2.com/display/AM300/Working+with+the+API+Microgateway
Design Goals
Following are some of the main expectations of Microgateway
- Ability to host just one or a selected set (subset) of APIs only.
- 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.
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 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 Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
-
Developer List: [email protected] | Subscribe | Mail Archive
-
User List: [email protected] | Subscribe | Mail Archive
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
-- The WSO2 API Manager Team --
Published by chamilaadhi about 6 years ago
The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0-RC3.
Introduction
The API Manager 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 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 (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
Documentation
https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway
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.
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.6.0-RC3
- 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 Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
-
Developer List: [email protected] | Subscribe | Mail Archive
-
User List: [email protected] | Subscribe | Mail Archive
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
-- The WSO2 API Manager Team --
Published by tharikaGitHub about 6 years ago
The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0-Alpha.
Introduction
The API Manager 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 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 (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
Documentation
https://docs.wso2.com/display/AM2xx/Working+with+the+API+Microgateway
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.
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.6.0-Alpha
- 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 Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
-
Developer List: [email protected] | Subscribe | Mail Archive
-
User List: [email protected] | Subscribe | Mail Archive
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
-- The WSO2 API Manager Team --
Published by chamilaadhi about 6 years ago
The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0-RC2.
Introduction
The API Manager 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 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 (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
Documentation
https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway
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.
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.6.0-RC2
- 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 Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
-
Developer List: [email protected] | Subscribe | Mail Archive
-
User List: [email protected] | Subscribe | Mail Archive
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
-- The WSO2 API Manager Team --
Published by tharikaGitHub about 6 years ago
The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0-RC1.
Introduction
The API Manager 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 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 (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
Documentation
https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway
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.
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.6.0-RC1
- 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 Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
-
Developer List: [email protected] | Subscribe | Mail Archive
-
User List: [email protected] | Subscribe | Mail Archive
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
-- The WSO2 API Manager Team --
Published by tharikaGitHub about 6 years ago
The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0-Beta.
Introduction
The API Manager 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 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 (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
Documentation
https://docs.wso2.com/display/AM2xx/Working+with+the+API+Microgateway
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.
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.6.0-Beta
- 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 Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
-
Developer List: [email protected] | Subscribe | Mail Archive
-
User List: [email protected] | Subscribe | Mail Archive
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
-- The WSO2 API Manager Team --
