What does an idempotent Kafka producer give you, and what is still not exactly-once to the database?
PICTURE THIS: DATABASE INDEX
Simple meaning
Idempotent producers prevent duplicate writes of the same produce batch to a partition after retries, using sequence numbers.
WHY — Kafka instead of guessing?
Why interviewers care about Kafka:
who only read docs from people who shipped.
and tied to Backend 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:
- 1Idempotent producers prevent duplicate
writes of the same produce batch to a partition after retries, using sequence numbers.
- 2Your consumer can still
process a message twice if it crashes after DB commit but before offset commit.
- 3End-to-end exactly-once needs transactional
produce plus an idempotent consumer or outbox.
- 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
Idempotent producers prevent duplicate writes of the same produce batch to a partition after retries, using sequence numbers. Your consumer can still process a message twice if it crashes after DB commit but before offset commit.