What is the primary difference between a reverse proxy and an API gateway?
A reverse proxy (like NGINX or HAProxy) handles Layer 7 connection termination, TLS offloading, static caching, and round-robin load distribution. An API gateway builds on top of this, adding application-level concerns: JWT authentication, OAuth2 validation, rate-limiting, request transformation, and route-based billing.
Answered in
The Building Blocks of Modern Systems: Web Servers, Proxies, API Gateways, CDNs, and DNSAn architectural guide to modern networking: core transport, naming and timing, security firewalls, ingress proxies, and identity infrastructure.
Read the full analysisOther questions this article answers
More networking questions
- Why is clock synchronization via NTP critical for distributed security and storage?
- How do Layer 4 switches differ from Layer 7 load balancers?
- What role does PKI (Public Key Infrastructure) play in modern zero-trust networks?
- What is the primary difference between a Service Mesh and an API Gateway?
- How do sidecar proxies intercept network traffic transparently?
- What is the latency cost of running a sidecar-based service mesh?
- What is a sidecar-less or ambient service mesh?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Networking beat.