Delivery & reliability
Transactional outbox
A transactional outbox records work to be dispatched in the same database transaction as the state that requires it, reducing the gap between committing data and scheduling an external action.
Also found under: Outbox pattern, Publication queue
How it works
A worker later processes pending outbox entries. The pattern separates acceptance from dispatch, but it still needs retry, expiry and deduplication policies. An internal publication queue is not a consumer-facing event history API and does not establish delivery to every browser.
In a Pubb integration
Pubb records accepted publications in an outbox before dispatch. Its HTTP 202 response identifies accepted work; clients should still keep durable application data and recovery logic in their own backend.
Publish an eventA practical example
An accepted publication can wait briefly for a dispatch worker. The publisher records its publicationId for tracking rather than interpreting the acceptance response as proof that every subscriber processed it.