Move long-running work into the background.
Email delivery, file conversion and large reports should not make users wait for a long HTTP response.
What matters for your application
Email and notification delivery
Prevent duplicate side effects when a job is processed again.
File processing and report generation
Define timeouts, retry budgets and a process for inspecting failed work.
Long-running synchronization with external services
Put resource references, rather than secrets, into job messages.
Where it fits
Email delivery, file conversion and large reports should not make users wait for a long HTTP response. Background workers process queued work separately from web requests.
- Email and notification delivery
- File processing and report generation
- Long-running synchronization with external services
Its place in your application
The API creates a job or message. A worker receives it, records the outcome and retries within limits after failures. Redelivery means the operation needs a safe repeatable design.
Before you begin
Choose services around the actual needs of your application. Include these points in your development and release plan.
- Prevent duplicate side effects when a job is processed again.
- Define timeouts, retry budgets and a process for inspecting failed work.
- Put resource references, rather than secrets, into job messages.
Common questions
Can the same job run more than once?
Queues may redeliver work after failures or disconnections. Side effects such as orders, mail or file generation need deduplication and idempotency.
Can I provision a live resource now?
Not yet. New registration and customer allocation are closed on the live site. Product guides are published; local development simulation does not create real services.