Why this matters
- VaultCommerce payment-to-ledger pipeline uses
read_committedconsumers and transactional producer. - transactional.id uniquely identifies a producer instance across restarts — fencing zombies.
- EOS does not cover external DB writes — pair with idempotent sink or outbox.
- Higher latency than non-transactional — use only where duplicates are unacceptable.
Begin transaction
Process
Commit transaction
Transaction flow
beginTransaction → produce to output topics → sendOffsetsToTransaction → commitTransaction. Abort on failure. Consumer sets isolation.level=read_committed to skip open transactions. VaultCommerce transactional.id=payment-ledger-pod-${POD_NAME}.
Key points
- transactional.id — fences stale producers; required for transactions
- read_committed — consumer isolation skipping uncommitted messages
- sendOffsetsToTransaction — atomic offset commit with output records
- Transaction coordinator — broker managing transaction state
- exactly_once_v2 — Kafka Streams EOS with improved protocol
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- Fencing and timeouts
- VaultCommerce rollout checklist
Test yourself
Answer these before moving on — recall is what makes it stick.