async-job-design

What problem does it solve?

Prevents asynchronous background work from silently failing or causing duplicate side effects by making delivery, retries, timeouts, cancellation, observability, and failure handling explicit and testable.

Core Features & Use Cases

• Idempotent job design: Defines how to derive an idempotency key, store replay outcomes, and handle conflicts when duplicates arrive.
• Bounded reliability: Specifies transient vs permanent vs rate-limited vs poison-message failure classes with capped retry attempts and exponential backoff with full jitter.
• Operational readiness: Requires structured logs, core metrics, DLQ/quarantine strategy, owner/runbook/alerts, and cancellation + compensation where side effects span steps.
• Use case: Designing a queue worker or workflow that processes event-driven business side effects (e.g., webhooks, fan-out tasks, backfills) without duplicate charges, emails, or inconsistent state.

Quick Start

Ask for a production-ready async job design that covers idempotency, retry/backoff, timeouts, DLQ quarantine, observability fields, cancellation semantics, and compensation for multi-step side effects.