Enterprise API Management

Sidecar API gateway

Problem statement:

In certain scenarios, it may not be desirable to have a single API microgateway mediating access to all service endpoints within an independent runtime (for example, Kubernetes clusters). Some of the reasons could be:

• Different services require fundamentally different gateway setups and therefore sharing a single one becomes highly impractical and restrictive.
• Separation of concerns: if an issue occurs in the shared microgateway infrastructure then all services are impacted.
• Freedom of choice: each sidecar gateway can effectively be from a different vendor.

Solution:

Instead of implementing an API microgateway as a replacement for an ingress load balancer, let the latter act as an API load balancer ...