Why reverse proxying serves backend applications in Nginx - Visual Breakdown

Process Flow - Why reverse proxying serves backend applications

Client sends request

↓

Reverse Proxy receives request

↓

Reverse Proxy forwards request to Backend

↓

Backend processes request

↓

Backend sends response to Reverse Proxy

↓

Reverse Proxy sends response to Client

The client sends a request to the reverse proxy, which forwards it to the backend server. The backend processes it and sends the response back through the proxy to the client.

Execution Sample

Nginx

server {
  listen 80;
  location / {
    proxy_pass http://backend_server;
  }
}

This nginx config sets up a reverse proxy that forwards all client requests to a backend server.

Process Table

Step	Action	Request State	Backend State	Response State
1	Client sends HTTP request to nginx reverse proxy	Request received by proxy	No action yet	No response yet
2	nginx reverse proxy forwards request to backend server	Request forwarded	Request received by backend	No response yet
3	Backend processes request	Request forwarded	Processing request	No response yet
4	Backend sends response to nginx reverse proxy	Request forwarded	Response sent	Response received by proxy
5	nginx reverse proxy sends response to client	Request completed	Response sent	Response sent to client
6	Connection ends	No active request	Idle	Client received response

💡 Request cycle completes when response is sent back to client and connection closes.

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
Request State	Not received	Received and forwarded	Forwarded, waiting response	Completed
Backend State	Idle	Request received	Response sent	Idle
Response State	No response	No response	Received by proxy	Sent to client

Key Moments - 3 Insights

Why does the client not communicate directly with the backend?

The client sends requests to the reverse proxy, which forwards them to the backend. This is shown in execution_table steps 1 and 2 where the proxy receives and forwards the request.

What happens if the backend is slow or down?

The reverse proxy can handle retries, caching, or show error pages. This is implied in step 3 and 4 where the backend processes or fails to respond, but the proxy manages the client connection.

Why is the response sent back through the reverse proxy?

The proxy controls the client connection and can modify or secure responses. Execution_table steps 4 and 5 show the backend sending response to proxy, which then sends it to client.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the backend first receive the client request?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Check the 'Backend State' column to see when the backend receives the request.

At which step does the reverse proxy send the response back to the client?

A Step 5

B Step 3

C Step 4

D Step 6

💡 Hint

Look for when 'Response sent to client' appears in the 'Response State' column.

If the backend is down and does not respond, which step would be delayed or missing?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Step 4 shows backend sending response; if backend is down, this step won't happen.

Concept Snapshot

Reverse proxy acts as a middleman between clients and backend servers.
Clients send requests to the proxy, not directly to backend.
Proxy forwards requests, receives backend responses, then sends them to clients.
Benefits include security, load balancing, caching, and hiding backend details.
Nginx config example: proxy_pass directive forwards requests to backend.

Full Transcript

When a client wants to access a backend application, it sends a request to the reverse proxy server instead of directly contacting the backend. The reverse proxy receives the request and forwards it to the backend server. The backend processes the request and sends the response back to the reverse proxy. Finally, the reverse proxy sends the response to the client. This setup helps protect the backend, balance load, and manage traffic efficiently. The nginx configuration uses the proxy_pass directive to forward requests to the backend server.