Moderate HTTP Question 79 of 226

What is HTTP keep-alive and why does it help APIs?

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

Keep-alive reuses a TCP connection for multiple HTTP requests instead of opening a new one each time.

WHY — HTTP instead of guessing?

Why interviewers care about HTTP:

HTTP questions separate people

who only read docs from people who shipped.

Keep it short, concrete,

and tied to Full Stack work.

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
Keep-alive reuses a TCP
connection for multiple HTTP requests instead of opening a new one each time.
2
That cuts handshake cost,
which matters for APIs that fire many small JSON calls.
3
HTTP/2 goes further with
multiplexing on one connection.
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

“That cuts handshake cost, which matters for APIs that fire many small JSON calls”

Break into beats

Thatcutshandshakecostwhichmatters

Speaking order

2987408337471632900

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

Key takeaway

Keep-alive reuses a TCP connection for multiple HTTP requests instead of opening a new one each time. That cuts handshake cost, which matters for APIs that fire many small JSON calls.