outbox-pattern

To persist domain events atomically with aggregates, this skill uses an outbox table to save events within the same transaction, ensuring data consistency before background processing publishes them asynchronously.

Guaranteed domain event delivery is achieved by persisting events to an outbox table transactionally, then using a scheduled background job with retry logic and backoff to process and publish them until successful.

You can process outbox messages by saving domain events via EF Core, triggering handlers through MediatR, and scheduling the background processing job using Quartz to ensure reliable asynchronous publication.

Idempotent handlers are required for background event processing to prevent duplicate side effects during retries, ensuring that reprocessing an outbox message after a failure does not corrupt system state.

Yes, the outbox pattern implementation supports batch processing of domain events and includes cleanup mechanisms for the outbox table to manage database growth after successful publication.

You should use an outbox table in transactional systems when you need atomic persistence of domain events alongside aggregates, requiring guaranteed delivery through background processing without data loss.