transactional-outbox
CommunityAtomic DB → Kafka with Outbox + CDC
System Documentation
What problem does it solve?
Transactional Outbox + CDC references describe how to solve the atomicity problem between persisting business data and emitting the corresponding event to a message broker. By storing the event in an outbox table within the same transaction and using Debezium to monitor and publish the change, you prevent inconsistencies such as lost or ghost messages.
Core Features & Use Cases
- Outbox table design with a matching JPA entity to persist business data and the outgoing event in a single transaction
- Debezium CDC integration to reliably route outbox changes to Kafka
- Optional polling publisher as a deterministic fallback for event delivery
- Idempotent consumers and recovery scenarios to maintain exactly-once-ish semantics
Quick Start
Implement the Outbox pattern by persisting both the business data and the outbox record in a single transaction, then enable Debezium CDC to stream outbox events to Kafka.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: transactional-outbox Download link: https://github.com/kssumin/claude-playground/archive/main.zip#transactional-outbox Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.