[IMAGE 1: upload 1.png. Caption: The CDN skips the server, the load balancer picks a server, and the API Gateway decides if a request is allowed.]
Picture a shopper opening a product page on a Flipkart-style store. In one second, the phone asks for a product photo, the shopper's cart and, somewhere else, a seller's system is updating stock through an API. Three requests, three very different needs.
The problem
These three terms get mixed up because all of them sit "in front of" the app. Without a clear split, teams make two kinds of mistakes:
Caching the wrong thing. A cart response cached at the edge can show one user's data to another.
Re-building the same checks in every service.…