Moderate Redis Question 121 of 226

When is Redis pub/sub the wrong choice compared with Kafka?

Java Specialist · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: HOW TO EXPLAIN IT

IdeaRedis

HowWhat happens inside

Why they askShows real use

Simple meaning

Redis pub/sub is fire-and-forget: if a subscriber is down, the message is gone.

WHY — Redis instead of guessing?

Why interviewers care about Redis:

They are checking judgment

on Redis.

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:

1
Redis pub/sub is fire-and-forget:
if a subscriber is down, the message is gone.
2
Kafka persists a log,
lets consumers replay from an offset, and scales with partitions.
3
Use Redis for ephemeral
fan-out like cache invalidation
4
use Kafka when you
cannot afford to lose events.
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

“Kafka persists a log, lets consumers replay from an offset, and scales with part”

Break into beats

Kafkapersistsalogletsconsumers

Speaking order

2987408337471632900

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

Key takeaway

Redis pub/sub is fire-and-forget: if a subscriber is down, the message is gone. Kafka persists a log, lets consumers replay from an offset, and scales with partitions.