Follow-up · depth 4
What trade-offs come with Kafka Exactly-Once Semantics?
What trade-offs come with Kafka Exactly-Once Semantics?
Answers use simple, clear English.
Audio N/AQuick interview answer
Pros: No duplicate downstream messages within pipeline. Cons: Higher latency; transactional overhead; not magic for external DB writes.
Detailed answer
Trade-offs for Kafka Exactly-Once Semantics: Pros: No duplicate downstream messages within pipeline. Cons: Higher latency; transactional overhead; not magic for external DB writes. Decision rule: choose Kafka Exactly-Once Semantics when the benefits outweigh operational cost for your SLO. Parent context: 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
Strong answers state both sides and when you would pick an alternative. 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
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 →