dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

updates per cassie 

Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>
This commit is contained in:
Hannah Hunter 2024-06-17 15:34:59 -04:00
parent b297b85312
commit 2cdf03ce77
1 changed files with 4 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
daprdocs/content/en/developing-applications/building-blocks/scheduler/scheduler-overview.md
View File

@ -6,13 +6,7 @@ weight: 1000
description: "Overview of the scheduler API building block"
---
The Scheduler API works as an orchestrator for scheduling jobs in the future, either at a specific time or a specific interval. The scheduler helps you with jobs like:
- Scalable actor reminders
- Scheduling any Dapr API to run at specific times or intervals, like when:
- Sending pub/sub messages
- Calling service invocations and input bindings
- Saving state to a state store
The Scheduler API works as an orchestrator for scheduling jobs in the future, either at a specific time or a specific interval. The scheduler helps you with scheduling jobs, including scalable actor reminders.
The Scheduler consists of two parts that work together to seamlessly schedule jobs across all of Dapr's API building blocks:
- The Scheduler building block
@ -26,6 +20,8 @@ The Scheduler building block is a job orchestrator, not executor. The design gua
- **Guaranteed:** A job is never invoked *before* the schedule is due.
- **Not guaranteed:** A ceiling time on when the job is invoked *after* the due time is reached.
All job details and user-associated data for scheduled jobs are stored in the embedded Etcd.
## Features
### Delayed pub/sub
@ -42,16 +38,7 @@ The Scheduler service enables the scheduling of jobs to scale across multiple re
### Scheduler reminders
Actors have actor reminders, but present some limitations involving scalability. Make reminders more scalable by using `ScheduleReminders`.
### Store job details separately from user-associated data
If you'd like to store your user-associated data in a specific state store of your choosing, then you can:
1. Provision a state store using the [Dapr state management building block]({{< ref howto-get-save-state.md >}}).
1. Set `jobStateStore ` as `true` in the state store component’s metadata section.
Setting the `jobStateStore` to `true` indicates that your user-associated data is stored in the state store of your choosing, but the job details are still stored in the embedded `etcd`. If the `jobStateStore` is not configured, then the embedded `etcd` is used to store _both_ the job details and the user-associated data.
Actors have actor reminders, but present some limitations involving scalability. Make reminders more scalable by using `SchedulerReminders`.
## Try out the Scheduler