Comparison
API gatewayvsRemote proxy
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 →Remote proxy
the call looked like an ordinary method on an ordinary object and it went over the network and timed out.
A local object standing in for one in another process, turning method calls into requests. Every generated gRPC or SOAP client is one. The pattern's most important lesson is a negative one: making a remote call look identical to a local call hides latency, partial failure and serialisation cost, which is the whole argument of the fallacies of distributed computing.
Full entry →