Jobs on Dapr Docs

Jobs overview

Mon, 01 Jan 0001 00:00:00 +0000

Many applications require job scheduling, or the need to take an action in the future. The jobs API is an orchestrator for scheduling these future jobs, either at a specific time or for a specific interval.

Not only does the jobs API help you with scheduling jobs, but internally, Dapr uses the Scheduler service to schedule actor reminders.

Jobs in Dapr consist of:

See example scenarios.

Features and concepts

Mon, 01 Jan 0001 00:00:00 +0000

Now that you’ve learned about the jobs building block at a high level, let’s deep dive into the features and concepts included with Dapr Jobs and the various SDKs. Dapr Jobs:

Provides a robust and scalable API for scheduling operations to be triggered in the future.
Exposes several capabilities which are common across all supported languages.
Supports sub-second precision when using duration values (for example 500ms). Actual trigger resolution may vary by runtime; Cron-based schedules are at the seconds level only.

Job identity

All jobs are registered with a case-sensitive job name. These names are intended to be unique across all services interfacing with the Dapr runtime. The name is used as an identifier when creating and modifying the job as well as to indicate which job a triggered invocation is associated with.

How-To: Schedule and handle triggered jobs

Mon, 01 Jan 0001 00:00:00 +0000

Now that you’ve learned what the jobs building block provides, let’s look at an example of how to use the API. The code example below describes an application that schedules jobs for a database backup application and handles them at trigger time, also known as the time the job was sent back to the application because it reached it’s dueTime.

Start the Scheduler service

When you run dapr init in either self-hosted mode or on Kubernetes, the Dapr Scheduler service is started.