Pattern 51 / CONSISTENCY
Use this when Reliably publishing events after a database write.
Outbox Pattern fits when Reliably publishing events after a database write. Mechanism: Persist the business change and outbound event in the same transaction; a relay later publishes pending events. Use it for Order workflows, audit events, domain events, integration events. The toll: Requires a relay, dedupe, monitoring, and cleanup of old outbox rows.
Order workflows, audit events, domain events, integration events.
Use outbox pattern when order workflows, audit events, domain events, integration events..
Describe the pressure first, then the mechanism, then the cost. That keeps the design grounded.
Same pressure family