async-jobs-and-events

To decouple domain event publishing from HTTP handlers, you can enqueue background jobs for asynchronous side effects and return immediately. This Skill automates queuing and worker processing to handle downstream notifications reliably outside the request cycle.

The outbox pattern for async background workers ensures reliable domain-event publishing by persisting events before dispatching them. This Skill applies outbox and pub-sub patterns to guarantee event delivery across bounded contexts without losing queued tasks.

Idempotent processing for queued domain events requires deterministic task execution and observable tracing. This Skill provides structured worker processing that safely retries asynchronous side effects without duplicating downstream notifications or data projections.

You need background jobs for domain events when handling IO, notifications, or projections that risk blocking HTTP responses. This Skill queues these asynchronous side effects to improve scalability and reliability across services and bounded contexts.

Yes, publisher-consumer decoupling across services is supported through structured event publishing. This Skill separates domain logic from HTTP handlers, allowing independent workers to process queued events and publish downstream notifications across bounded contexts.

To add observability and tracing to asynchronous workers, you need structured background processing that tracks queued events. This Skill integrates tracing into worker execution, providing visibility into domain-event publishing and asynchronous side effects.