How do you implement the outbox pattern with RabbitMQ?

The outbox pattern solves the dual-write problem: atomically persisting data to a database AND publishing a message to RabbitMQ. Without the outbox: if you save to DB then publish to RabbitMQ, a failure between the two steps causes inconsistency (DB saved, message not sent, or vice versa). With the outbox: 1. Atomic write: in the same database transaction as the business operation, write the event to an outbox table: INSERT INTO outbox (event_type, payload, created_at) VALUES (...). 2. Outbox publisher: a separate process polls the outbox table for unpublished events, publishes to RabbitMQ with publisher confirms, and marks as published on success. Transactional outbox with Debezium: use CDC to capture outbox table changes and stream them to RabbitMQ/Kafka via Debezium connector — no polling needed. Result: the business operation and message publishing are eventually consistent but never inconsistent. The outbox can be retried on RabbitMQ failures without risking data loss. The outbox pattern is considered best practice for event-driven microservices.