API microgateway
Problem statement:
An independent runtime has been implemented as the main runtime for fully decoupled services (microservices). Adopting an API gateway as a resource router into the runtime can be inefficient because typical independent runtimes, such as Kubernetes, make use of an ingress load balancer as an entry point to internal services.
While the approach mentioned would work, it also implies a two-layer API gateway architecture, adding complexity and additional compute costs. The outer gateway acts as a policy enforcement point and router into the ingress, and the ingress itself acts as an API load balancer into service endpoints inside the runtime.
Solution:
A better solution would be for the ingress load balancer ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access