High Kafka Question 195 of 226

Your consumer must tolerate duplicate Kafka messages. What is the practical pattern?

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

PICTURE THIS: DATA SPLIT

Train 70%Val 15%Test 15%

Fit on train, tune on val, report on test once.

Simple meaning

Store a unique event id or (topic, partition, offset) in a processed table with a unique constraint, and ignore duplicates.

WHY — Kafka instead of guessing?

Why interviewers care about Kafka:

Kafka questions separate people

who only read docs from people who shipped.

Keep it short, concrete,

and tied to Backend 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
Store a unique event
id or (topic, partition, offset) in a processed table with a unique constraint, and ignore duplicates.
2
Make the side effect
itself idempotent, like UPSERT.
3
Do not rely on
Kafka exactly-once if you write to a system that is outside the Kafka transaction.
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

“Make the side effect itself idempotent, like UPSERT.”

Break into beats

Makethesideeffectitselfidempotent

Speaking order

2987408337471632900

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

Key takeaway

Store a unique event id or (topic, partition, offset) in a processed table with a unique constraint, and ignore duplicates. Make the side effect itself idempotent, like UPSERT.