How do nginx upstream keepalive and load-balancing methods affect Node?
PICTURE THIS: STACK VS QUEUE
Simple meaning
keepalive reuses connections from nginx to Node, cutting handshake overhead.
WHY — nginx instead of guessing?
Why interviewers care about nginx:
question about nginx.
trade-offs, and what you would actually do on a Full Stack project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1keepalive reuses connections from
nginx to Node, cutting handshake overhead.
- 2Algorithms such as least_conn
send new requests to the busiest-capable worker rather than blindly round-robin.
- 3Mis-sized upstreams and missing
keepalive cause extra latency under load.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
keepalive reuses connections from nginx to Node, cutting handshake overhead. Algorithms such as least_conn send new requests to the busiest-capable worker rather than blindly round-robin.