About Scheduled¶

Scheduled¶

Scheduled's objective is to provide a way to describe scheduled jobs in an intuitive way, having the minimal configuration necessary to cover the majority of use cases.

This would make it easier for developers to define when scheduled recurrent tasks should run, without having to check additional manuals or online resources to understand how to configure the schedule.

At the same time, as it doesn't enforce declaring a precise time for each configuration but only a cadence, it allows providers to implement the actual scheduling distributing work uniformly, avoiding spikes in resource usage.

This avoids the common problem of most cron providers, where most jobs start at the same time at midnight UTC, even while that is not necessary for most cases, but ends up accidentally enforced by the cron syntax.

Alternatives¶

This is primarily an alternative to using cron, with the crontab syntax.

Scheduled intentionally doesn't cover all the possible configurations cron would support.

The same way, it doesn't enforce declaring all the configurations cron would need set even for the simplest use cases.