Follow-up · depth 8
Compare Kafka Exactly-Once Semantics with a common alternative in a design review
Compare Kafka Exactly-Once Semantics with a common alternative in a design review
Answers use simple, clear English.
Audio N/AQuick interview answer
Compare Kafka Exactly-Once Semantics vs the usual alternative on complexity, latency, failure modes, and ops cost. Pros: No duplicate downstream messages within pipeline. Cons: Higher latency; transactional overhead; not magic for external DB writes.
Detailed answer
Design-review comparison for Kafka Exactly-Once Semantics: Axes: correctness, latency, throughput, complexity, operability. From the topic: Pros: No duplicate downstream messages within pipeline. Cons: Higher latency; transactional overhead; not magic for external DB writes. Recommendation: pick Kafka Exactly-Once Semantics when its strengths match the SLO; otherwise choose the alternative and say why. Parent context: Baseline: Idempotent producer + transactional writes (read-process-write in one transaction) give EOS within Kafka. End-to-end EOS needs idempotent sinks or outbox pattern.
Full explanation
Show a clear decision framework, not “it depends” with no criteria. Pros: No duplicate downstream messages within pipeline. Cons: Higher latency; transactional overhead; not magic for external DB writes.
Follow-up questions
Only answered follow-ups are shown — click to open with full answers
Parent context — Kafka Exactly-Once Semantics
Baseline: Idempotent producer + transactional writes (read-process-write in one transaction) give EOS within Kafka. End-to-end EOS needs idempotent sinks or outbox pattern.
View full parent question →