Notes / Event-driven Java

Event-driven Java where money moves

Event-driven architecture is well documented right up to the point where it meets a real database, a real compliance requirement and a consumer owned by another team. These notes are about that point: replay safety, write-ahead log pressure, schema evolution across organizational boundaries, and audit trails that survive review.

Covered here

Kafka
Debezium CDC
Transactional outbox
Idempotency
Avro schema evolution
Audit trails

1 note

Event-driven Java7 Sept 20266 min

Idempotency keys are not enough when money moves

At-least-once delivery means your consumer will see the same message twice. Why a deduplication table alone is insufficient for financial operations, and what to add.