How is Redis used as a cache in a Node API?
PICTURE THIS: STACK VS QUEUE
Simple meaning
The API checks Redis for a key, returns the value on a hit, and on a miss loads MongoDB then writes Redis with a TTL.
WHY — Caching instead of guessing?
Why interviewers care about Caching:
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:
- 1The API checks Redis
for a key, returns the value on a hit, and on a miss loads MongoDB then writes Redis with a TTL.
- 2Redis is fast and
shared across Node processes.
- 3Use it for hot
reads, sessions, and rate-limit counters.
- 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
The API checks Redis for a key, returns the value on a hit, and on a miss loads MongoDB then writes Redis with a TTL. Redis is fast and shared across Node processes.