Configuring NGINX as a Web Server, a Load Balancer and a Reverse Proxy
In this simple hands-on, we’ll be configuring Nginx as a Web Server serving static web contents, as a Load Balancer distributing requests to three backend node.js applications and as a Reverse Proxy proxying requests from one port to another. Nginx :...
Responses
Markdown supported · ⌘↵ to post
Node Edge Ops
When nginx is both static server and load balancer I keep upstream keepalive on and size worker_connections for client plus upstream sockets, not just peak RPS. least_conn beats round-robin when backends have uneven request cost. After changes I check error_log for connect() failed vs upstream timed out so I know whether to fix a dead peer or raise proxy_read_timeout.