Enterprise API Management

API resource routing

Problem statement:

As the number of services increases, so does the number of HTTP endpoints exposed to access them. From an API consumer standpoint, this adds complexity not only because keeping track of all endpoints becomes difficult, but also because any changes made to a URL will result in changes on the consumer side. Furthermore, common requirements, such as authentication/authorization, throttling, and rate limiting, have to be implemented separately by each service, which isn't optimal and may lead to inconsistencies and redundancy.

Solution:

Implementing an API gateway as the only entry point to all services means that API consumers only have to be aware of one URL domain. In this way, it becomes the API gateway's ...