When you need to expose this service to the outside in a managed way, the API developer can use the WSO2 API Publisher Portal to create the API by attaching necessary policies like security, rate limiting etc. The Publisher is capable of pushing all these policies in to the Envoy proxy via the Pilot and Mixer in order for them to take action with regard to the policy enforcement. After publishing the API, it will appear in the WSO2 API Developer Portal. Thereafter, the app developer can discover these APIs and use them in their application along with all the capabilities provided by the developer portal such as, getting a subscription plan, adding application security etc. If you are a business user, you can use WSO2 API-M Analytics to get more business insights by looking at the API Analytics.
- The client sends the request to the service (Istio capture the request and redirects it to the Istio-proxy). This enters the Kubernetes cluster via an ingress point.
- The Istio proxy captures a wealth of signal and sends it to the Mixer as attributes.
- The Mixer adapter then calls the WSO2 API Manager for various types of policy checks and verifications.
- WSO2 API Manager performs the policy checks and responds back to the Mixer.
- The Mixer communicates the outcome of the policy checks to the Istio proxy.
- When there are no policy validation failures, the request is routed to the microservice.
- The microservice executes the service logic and sends the response.
- The response is sent out to the client.
Install Istio for WSO2 API Manager
For more information, see Istio for WSO2 API Manager Quick Start guide.