Enterprise API Management

API geo-routing

Problem statement:

An API has global reach with consuming applications spread all over the world. In order to prevent latency issues and other unforeseen issues that may occur due to distance (for example, a consuming application from Asia calling an API located in North America), API gateways and other service infrastructure have been deployed in multiple regions across the world as needed (for example, in support of data sovereignty requirements). The challenge remains, however, of deciding the most effective way for consuming applications to determine what localized URL they should be using.

Multiple options exist but they are deemed sub-optimal, for example, using different sub-domains for each API gateway in each region ...