Ongoings
Queues, schedules, background jobs and workflows.
Ongoings runs work outside the request path. It durably accepts your events and work, runs it with clear delivery and execution rules, and shows you what happened, including retries, cancellations and failures.
What Ongoings handles
Ongoings is designed to cover the areas below. Capabilities become available as the Ongoings interface is released.
| Area | Description |
|---|---|
| Queues | Work outside the request path. |
| Schedules | Jobs on a recurring timetable, or once at a set time. |
| Background jobs | Jobs dispatched to workers, with attempts, timeouts, cancellation and results. |
| Workflows | Multi-step workflows with run history. |
| Events | Events and triggers that start work. Topics are planned. |
| Failure handling | Retries and failure inspection per run. |
Design for repeats
Ongoings runs work at least once. A step can run more than once, so make its side effects safe to repeat. See Execution semantics.
Ongoings and Runtime
Which product to use for which work.
Execution semantics
At-least-once execution, retries, timeouts and cancellation.
Concepts
Jobs, workflows, runs, attempts, workers and schedules.
Available at release
Quickstarts, SDK installation and the API reference are published when the Ongoings interface is released.