Why put email sending on a queue instead of the request thread?
PICTURE THIS: A REST CALL
ClientGET /users/1
ServerFind row
JSON back200 OK
Simple meaning
SMTP is slow and flaky.
WHY — Queues instead of guessing?
Why interviewers care about Queues:
They are checking judgment
on Queues.
A good answer names
the situation, the default choice, and one exception - that reads as experience.
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:
- 1Define it
SMTP is slow and flaky.
- 2A worker retries without
blocking the HTTP response.
- 3The API returns quickly
and the user still gets the mail.
- 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:
Say this line
“A worker retries without blocking the HTTP response.”
Break into beats
Aworkerretrieswithoutblockingthe
Speaking order
2987408337471632900
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
SMTP is slow and flaky. A worker retries without blocking the HTTP response.