<h3 id="heading-overview">Overview</h3>
<p>Gateway is a very common pattern in a microservice architecture. However, in certain scenarios, we need a very light installation, not a so big one. So, I come up with a PoC for WSO2 Microgateway.</p>
<p>WSO2 Microgateway is a product of WSO2 company which provides the API gateway capabilities</p>
<ul>
<li><p>Authentication and authorization</p>
</li>
<li><p>Traffic Throttling</p>
</li>
<li><p>API management</p>
</li>
</ul>
<p><img src="https://mg.docs.wso2.com/en/latest/assets/img/api-mg-overview.png" alt="Microgetway" /></p>
<h3 id="heading-differences-with-api-management">Differences with API Management</h3>
<div class="hn-table">
<table>
<thead>
<tr>
<td>Feature</td><td>Microgateway</td><td>API Management</td></tr>
</thead>
<tbody>
<tr>
<td><em>Architecture</em></td><td>Simple, for microservice</td><td>Complex, for monolith</td></tr>
<tr>
<td><em>API Lifecycle</em></td><td>OAS fully compatible</td><td>Create/Update/Destroy Manually; Partially support OAS</td></tr>
<tr>
<td><em>Update API</em></td><td>Immutable</td><td>Mutable, update with UI</td></tr>
<tr>
<td><em>Horizontal scale</em></td><td>Scales independently at runtime does not have a direct dependency on other components</td><td>Scaling can be done with other components. For example, the traffic manager</td></tr>
<tr>
<td><em>Easy to use</em></td><td>Require popular knowledge only (OAS, CLI)</td><td>Experience with WSO2 product + popular knowledge (OAS, CLI)</td></tr>
<tr>
<td><em>Memory Consumption</em></td><td>~ 250 MB for normal load</td><td>~ 2,2 GB for normal load</td></tr>
</tbody>
</table>
</div><p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1669258502376/nk0jFdHCF.png" alt="MicrosoftTeams-image.png" /></p>


### Overview

Gateway is a very common pattern in a microservice architecture. However, in certain scenarios, we need a very light installation, not a so big one. So, I come up with a PoC for WSO2 Microgateway.

WSO2 Microgateway is a product of WSO2 company which provides the API gateway capabilities

* Authentication and authorization
    
* Traffic Throttling
    
* API management
    

![Microgetway](https://mg.docs.wso2.com/en/latest/assets/img/api-mg-overview.png align="left")

### Differences with API Management

| Feature | Microgateway | API Management |
| --- | --- | --- |
| *Architecture* | Simple, for microservice | Complex, for monolith |
| *API Lifecycle* | OAS fully compatible | Create/Update/Destroy Manually; Partially support OAS |
| *Update API* | Immutable | Mutable, update with UI |
| *Horizontal scale* | Scales independently at runtime does not have a direct dependency on other components | Scaling can be done with other components. For example, the traffic manager |
| *Easy to use* | Require popular knowledge only (OAS, CLI) | Experience with WSO2 product + popular knowledge (OAS, CLI) |
| *Memory Consumption* | ~ 250 MB for normal load | ~ 2,2 GB for normal load |

![MicrosoftTeams-image.png](https://cdn.hashnode.com/res/hashnode/image/upload/v1669258502376/nk0jFdHCF.png align="left")

Tech Notes

Tech Notes

Get started with Microgateway

Overview

Differences with API Management

Feature	Microgateway	API Management
Architecture	Simple, for microservice	Complex, for monolith
API Lifecycle	OAS fully compatible	Create/Update/Destroy Manually; Partially support OAS
Update API	Immutable	Mutable, update with UI
Horizontal scale	Scales independently at runtime does not have a direct dependency on other components	Scaling can be done with other components. For example, the traffic manager
Easy to use	Require popular knowledge only (OAS, CLI)	Experience with WSO2 product + popular knowledge (OAS, CLI)
Memory Consumption	~ 250 MB for normal load	~ 2,2 GB for normal load