What is backpressure in Node streams?
PICTURE THIS: STACK VS QUEUE
Simple meaning
Backpressure is the signal that a writable destination is slower than the readable source.
WHY — Node.js instead of guessing?
Why interviewers care about Node.js:
who only read docs from people who shipped.
and tied to Full Stack work.
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:
- 1Backpressure is the signal
that a writable destination is slower than the readable source.
- 2If you ignore pause
and drain, memory grows until the process dies.
- 3pipe() and modern pipeline
helpers handle much of this for you.
- 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
Backpressure is the signal that a writable destination is slower than the readable source. If you ignore pause and drain, memory grows until the process dies.