Business event delivery

The Lifecycle

Transitions Explained

Publication captures an event with its write. Dispatch queues work only for configured handlers; unmatched transport is discarded without notifying a receiver. Consumer failure asks the queue to retry, eventually isolating persistent failure in the dead-letter queue.

What Cannot Happen

Rolled-back writes retain no published event. Successful queue settlement removes that message, but duplicates remain possible around transport acknowledgement; receivers must deduplicate.

Concurrency and Timing

The dispatcher runs every minute, which is a schedule interval rather than a delivery guarantee. Receiver availability, retries and configuration determine actual delay, and no ordering guarantee is provided.