Exactly-once semantics (EOS) in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does Exactly-once semantics (EOS) mean in Kafka?

EOS ensures that each message is processed exactly one time, preventing duplicates or data loss even in failures.

intermediate

How does Kafka achieve Exactly-once semantics?

Kafka uses idempotent producers and transactional APIs to guarantee messages are written and processed exactly once.

beginner

What is an idempotent producer in Kafka?

An idempotent producer ensures that resending the same message does not create duplicates, helping EOS.

intermediate

What role do transactions play in Kafka's EOS?

Transactions group multiple writes and commits so they either all succeed or all fail, ensuring atomicity and EOS.

beginner

Why is Exactly-once semantics important in real-world applications?

It prevents duplicate processing or data loss, which is critical for financial systems, order processing, and analytics.

What does Exactly-once semantics guarantee in Kafka?

A Messages can be duplicated but not lost

B Messages can be lost but not duplicated

C Each message is processed only once

D Messages are processed at least once

Exactly-once semantics means each message is processed exactly one time, no duplicates or losses.

Which Kafka feature helps avoid duplicate messages when resending?

A Idempotent producer

B Consumer groups

C Partitioning

D Replication

Idempotent producers ensure resending the same message does not create duplicates.

What does Kafka use to group multiple writes atomically for EOS?

A Transactions

B Partitions

C Offsets

D Consumer commits

Transactions allow grouping writes so they succeed or fail together, ensuring EOS.

Which scenario benefits most from Exactly-once semantics?

A Caching static content

B Financial transaction processing

C Logging debug messages

D Streaming video playback

Financial transactions require no duplicates or losses, so EOS is critical.

If a Kafka producer is not idempotent, what can happen?

A Messages will be lost

B Messages will be compressed

C Messages will be encrypted

D Duplicate messages may be produced

Without idempotency, resending can cause duplicate messages.

Explain how Kafka achieves Exactly-once semantics using idempotent producers and transactions.

Think about how Kafka avoids duplicates and ensures atomic writes.

Why is Exactly-once semantics important in systems like financial applications?

Consider what happens if money is counted twice or lost.