Kafka mendukung jaminan pengiriman yang berbeda — at-most-once, at-least-once, dan exactly-once — yang menentukan apakah pesan dapat hilang atau terduplikasi. Memahami hal ini dan cara mencapainya penting untuk membangun sistem yang andal.
Tiga semantik pengiriman
AT-MOST-ONCE → messages may be LOST but never duplicated:
→ commit offset BEFORE processing → if processing fails, the message is skipped (lost)
→ for: when occasional loss is acceptable and duplicates are not (rare)
AT-LEAST-ONCE → messages are never lost but may be DUPLICATED:
→ commit offset AFTER processing → if a crash occurs before commit, the message is
reprocessed (duplicate) → requires IDEMPOTENT processing
→ the common default; safe (no loss) but handle duplicates
EXACTLY-ONCE → each message is processed exactly once (no loss, no duplicates):
→ the strongest, but hardest; requires Kafka transactions + idempotent producers
