API load balancing
In traditional API gateway implementations, there tends to be a load balancer situated in between the gateway and the service endpoints. The problem with this architecture is that unless the load balancer itself is capable of automatically detecting added and/or removed service endpoints (for example, during a service scale up or down), customizations are required in the load balancer infrastructure in order for it to be dynamically configured for such rapid and sudden changes.
Instead, this capability refers to the ability of an API gateway to also act as a client-based load balancer, thus removing the need for a load balancer in between. The consequence of this is that the API gateway should have the ability to introspect ...
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