How to Implement Nginx Static‑Dynamic Separation for Faster Web Performance

Nginx is a core component in large‑scale architectures. Static‑dynamic separation means handling static assets (HTML, CSS, JavaScript, images, fonts, video, etc.) separately from dynamic requests that require server‑side rendering, database interaction, or session handling.

Static Resource Architecture

Nginx serves static files directly, leveraging kernel cache, sendfile, and asynchronous I/O to minimize context switches and system calls. Static assets are typically placed in a dedicated directory or served from a separate domain/sub‑domain.

Example location block for caching common static file types:

location ~* \.(jpg|jpeg|png|gif|ico|css|js|woff|woff2|eot|svg|webp|html)$ {
    expires 30d;
    add_header Cache-Control "public";
}

Static caching strategies combine browser cache, Nginx proxy cache, and CDN cache. Use long‑term caching for static files and short‑term (5–60 seconds) or versioned caching for dynamic API responses to avoid data inconsistency.

Dynamic Request Routing Architecture

Dynamic requests are proxied to backend application servers (e.g., Tomcat, Gunicorn, Node.js) via an upstream definition. Load‑balancing methods such as round‑robin, weighted, least‑connections, or IP‑hash can be applied.

Sample upstream and location configuration for dynamic APIs:

upstream backend_upstream {
    server app1.internal:8080;
    server app2.internal:8080;
    server app3.internal:8080;
}

location /api/ {
    proxy_pass http://backend_upstream;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_read_timeout 60;
    proxy_connect_timeout 5;
}

Dynamic content caching should be used cautiously; only cache safe endpoints with short TTL or segment caching to maintain data consistency.

Phased Migration Steps

Separate static resource domain and apply optimized caching policies.

Introduce backend upstream clusters with health checks.

Finally, integrate a CDN for further performance gains.

By following these steps, static assets are served efficiently while dynamic requests are balanced across application servers, resulting in reduced resource contention and lower response latency.