Pattern 41 / INFRA

Reverse Proxy

Use this when putting common web concerns in front of application servers.

Pressure
Putting common web concerns in front of application servers
Mechanism
Proxy receives client traffic and handles tls, compression, routing, buffering, and caching
Toll
Incorrect headers/routing can hide client identity or create difficult bugs
Architecture plate41
Diagram for Reverse Proxy
Executive brief

Reverse Proxy fits when putting common web concerns in front of application servers. Mechanism: proxy receives client traffic and handles TLS, compression, routing, buffering, and caching. Use it for almost every production web deployment. The toll: incorrect headers/routing can hide client identity or create difficult bugs.

Use when

Almost every production web deployment.

Example

Nginx or caddy terminating https before app containers.

Review framing

Describe the pressure first, then the mechanism, then the cost. That keeps the design grounded.

Same pressure family

Infrastructure Patterns

40CDN (Content Delivery Network)42Service Mesh43Sidecar Pattern
← 4042 →