High Express Question 154 of 226

How do you implement graceful shutdown for Express?

MERN Full Stack · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: A REST CALL

ClientGET /users/1

ServerFind row

JSON back200 OK

Simple meaning

On SIGTERM stop accepting new connections, finish in-flight requests, close the HTTP server, then close MongoDB and Redis.

WHY — Express instead of guessing?

Why interviewers care about Express:

This is a process

question about Express.

Panels listen for order,

trade-offs, and what you would actually do on a Full Stack project - not buzzwords.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

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:

1
On SIGTERM stop accepting
new connections, finish in-flight requests, close the HTTP server, then close MongoDB and Redis.
2
A shutdown timeout should
force exit so Kubernetes does not hang.
3
Health probes should fail
as soon as shutdown starts so the load balancer drains traffic.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line

“A shutdown timeout should force exit so Kubernetes does not hang.”

Break into beats

Ashutdowntimeoutshouldforceexit

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

On SIGTERM stop accepting new connections, finish in-flight requests, close the HTTP server, then close MongoDB and Redis. A shutdown timeout should force exit so Kubernetes does not hang.