Transactional outbox

Write the business change and the event to publish in the same database transaction, then relay the event to the broker. It avoids losing events or publishing events for changes that rolled back.

Where it shows up in real systems

  • Change data capture

    Keeps search indexes, caches and warehouses in sync without dual writes in the application, which can drift when one write fails. Consumers see changes a fraction of a second later.

    In production: Debezium, AWS DMS, Kafka Connect, Google Datastream, Fivetran

See it break, then fix it

Build an architecture, send it a day of traffic and outages, and learn why it holds or fails. Free to start.

Open the learning path Open the sandbox