Comparison
API gatewayvsIngress
API gateway
you put one component in front of all the services to do auth, rate limiting and routing once instead of in each of them.
A single entry point handling cross-cutting concerns — authentication, rate limiting, routing, request logging — for services behind it. It removes duplicated middleware and gives one place to enforce policy. It is also a shared choke point and a place for business logic to accumulate where nobody owns it.
Full entry →Ingress
traffic from outside arrives at one front door with the certificate on it, and is routed inwards by hostname and path.
Traffic entering a cluster or network boundary from outside, and the configuration describing how it is routed once it arrives. It is where TLS termination, external DNS, WAF rules and public routing all live, so it is a shared, contended object across teams. It is also the natural chokepoint for rate limiting and authentication, which is why it accretes responsibilities until somebody calls it an API gateway.
Full entry →