An API gateway receives API traffic and applies gateway functions such as routing, access management, and developer credential handling. section 7.1.3
For third-party API access, DNS can direct api.epetech.io to the gateway, which then forwards traffic to the actual API. section 7.1.3
Use an API gateway selectively:
- Prefer it when third-party developers need a controlled external API entry point. section 7.1.3
- Avoid adding it automatically to Kubernetes services when the Kubernetes API or service mesh already supplies the required capabilities. section 7.1.3
- Account for additional traffic, configuration complexity, cost, and potential customer-support burden. section 7.1.3
External API traffic
An engineering platform exposes APIs at api.epetech.io. DNS points that subdomain to the API gateway, which redirects requests to the deployed API while supporting third-party access. section 7.1.3





