Proxy vs Reverse Proxy: A Simple Mental Model

Proxy and reverse proxy were two networking concepts that I found surprisingly confusing at first.

The easiest way I now remember the difference is:

Proxy → hides the client
Reverse Proxy → hides the server

A forward proxy sits between a client and the internet.

Client → Proxy → Server

The server communicates with the proxy instead of directly seeing the original client.

A reverse proxy works from the other direction.

Client → Reverse Proxy → Backend Server

The client communicates with the reverse proxy without necessarily knowing which backend server handles the request.

Reverse proxies are commonly used for things like load balancing, HTTPS termination, routing requests, and protecting backend services.

For example, a website might have several backend servers, but users only connect to one public address. A reverse proxy such as Nginx can decide which backend should receive each request.

Learning this distinction also helped me understand modern web architectures better, especially how frontend applications, APIs, gateways, and backend services communicate.