Mental model
A Reverse Proxy acts as an edge gateway positioned in front of backend application servers. It terminates TLS/SSL certificates, inspects incoming HTTP request paths, compresses responses, and balances traffic across upstream server clusters.
Public HTTPS Request
Nginx/Traefik Reverse Proxy (TLS Termination)
Load Balance across Upstream Cluster
Forward via Keep-Alive Sockets to FastAPI
Theory
- TLS Termination: Decrypts HTTPS traffic at the edge proxy, allowing internal microservice communication over fast unencrypted HTTP within isolated private networks.
- Upstream Connection Pooling: Reuses persistent TCP connections between the reverse proxy and backend application servers (
proxy_http_version 1.1; proxy_set_header Connection "";).
nginx(26 lines)
1# Nginx production reverse proxy configuration
2upstream fastapi_backend {
3 least_conn; # Route to server with fewest active connections
4 server 10.0.1.10:8000 max_fails=3 fail_timeout=;
5 server 10.0.1.11:8000 max_fails=3 fail_timeout=;
6 keepalive 32; # Maintain 32 persistent backend sockets
7}
8
9server {
10 listen 443 ssl http2;
11 server_name fullstackaihub.com;
12
13 ssl_certificate /etc/letsencrypt/live/fullstackaihub.com/fullchain.pem;
14 ssl_certificate_key /etc/letsencrypt/live/fullstackaihub.com/privkey.pem;
15
16 location / {
17 proxy_pass http://fastapi_backend;
18 proxy_http_version 1.1;
19 proxy_set_header Connection "";
20 proxy_set_header Host $host;
21 proxy_set_header X-Real-IP $remote_addr;
22 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
23 proxy_set_header X-Forwarded-Proto $scheme;
24 }
25}
6 lines hidden
Alternatives and trade-offs
- Direct Application Exposure: Simple; forces web application workers to manage TLS certificates, static file serving, and DDoS filtering.
- Reverse Proxy Gateway (Nginx / Traefik): High performance edge security, static file caching, and seamless zero-downtime rolling deployments.
Failure modes and misconceptions
- Missing
X-Forwarded-ForHeaders: Failing to setX-Forwarded-Forcauses application logs and rate limiters to see the reverse proxy internal IP address for all client requests. - HTTP/1.0 Default Proxy Pass: Nginx defaults to
proxy_http_version 1.0, which closes backend TCP sockets after every request. Always explicitly configure HTTP/1.1 with persistent keep-alive connections.
Reflect before revealing the guide
Decision scenario
Deploy Nginx or Traefik as the reverse proxy edge router in front of containerized FastAPI pods to handle TLS termination, Gzip/Brotli compression, and upstream load balancing.
Learning outcomes
- Configure TLS termination and modern SSL cipher suites at the edge.
- Implement upstream load-balancing strategies (Round Robin, Least Connections, IP Hash).
- Enable persistent HTTP/1.1 keep-alive connection pools between proxy and backend apps.
Trade-offs
Reverse proxies add an extra network hop to request latency, but provide essential edge security, TLS termination, and traffic management capabilities.