Today, thousands of microservices are replacing hundreds of enterprise apps within an organization—driving exponential growth in the number of programmable endpoints handled by APIs. WSO2 API Microgateway simplifies the process of creating, deploying and securing APIs within distributed microservice architectures.
Microgateways are most useful to:
Expose microservices as managed APIs
Compose one or more microservices to be exposed as APIs
Apply security to internal and external microservices
Obtain business insights from the consumption of microservices
Expose legacy services/microservices as modern APIs
Benefits of WSO2 API Microgateway
Cloud-native; ideal for network-distributed integration
Lightweight stateless container with low memory footprint, fast bootup time, and built-in capabilities for automated CI/CD workflows.
Developer-first and ops friendly
Uses the OpenAPI Specification (OAS), which means developers can collaborate in creating APIs and then test them independently.
Support for transforming legacy API formats
The microgateway can transform API requests and responses from legacy formats to modern ones, so they can be exposed to modern consumer apps.
Support for composing multiple microservices
Enables developers to expose a combination of microservices via a single API in line with modern best practices.
Run-time service discovery
The microgateway automatically discovers microservices, which often see IP address changes as a result of being redeployed.
The microgateway can run in isolation with no dependencies on other components, which enables greater scalability and smoother upgrades.
The Role of API Microgatway in Microservices
API Microgateway Developer Workflow
- Download the toolkit and setup the environment
- Define your APIs using
- the Open API Specification and add the microgateway
- specific vendor extensions
- Initialize a microgateway project,
- add the open API files and
- build the project
- Deploy the microgateway
- (on a VM, on Docker or on Kubernetes) using
- the build artifacts from the project
- Test the API using REST/SOAP clients,
- debug and fix it
- Push project to source control (Git),
- create immutable Docker images and
- push to Docker registry