Kafka guarantees require configuration and scope#
At-least-once processing is common when a consumer performs a side effect before committing its offset. Producer retries, idempotent producer behavior, transactions, and offset commits influence duplicates and ordering.
| Boundary | Useful mechanism | Still unresolved |
|---|---|---|
| Producer → Kafka | Acknowledgements and idempotent production | Application request identity |
| Kafka → Kafka | Transactions for supported read/process/write workflows | External systems |
| Kafka → database/payment | Idempotent consumer and transactional state | Cross-system side-effect coordination |
Related practice problems
Use the manifest-backed prompts below to apply this lesson in a complete design.
- Kafka design and delivery semanticsApache Kafka Documentation
Reach this point to mark the lesson as read.