Configure Debezium outbox event router SMT to implement the transactional outbox pattern for reliable event publishing

domain: debezium.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create an outbox table with columns: id (UUID PK), aggregatetype, aggregateid, type, payload (JSON), and timestamp; insert rows within the same database transaction as the domain change
  2. Configure the outbox SMT: transforms=outbox,transforms.outbox.type=io.debezium.transforms.outbox.EventRouter
  3. Set transforms.outbox.table.field.event.id=id, transforms.outbox.table.field.event.key=aggregateid, transforms.outbox.table.field.event.payload=payload, transforms.outbox.route.by.field=aggregatetype
  4. Set transforms.outbox.table.expand.json.payload=true to deserialize the payload column as a structured JSON object rather than a raw string in the Kafka record value
  5. Optionally set transforms.outbox.route.topic.replacement to a topic naming template; the aggregatetype value becomes the Kafka topic name by default

Known gotchas

Related routes

Implement exactly-once CDC delivery using the transactional outbox pattern with Debezium and Kafka
debezium.io · 5 steps · unrated
Route Debezium change events to per-table Kafka topics using the topic routing SMT (ByLogicalTableRouter) and a custom routing regex
debezium.io · 5 steps · unrated
Configure Debezium signaling table for ad-hoc incremental snapshots
debezium.io · 6 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans