Deno adds Deno Cron for job scheduling

"Announced November 29 and available behind the --unstable flag in Deno 1.38, Deno.cron() is a function that takes three parameters: the name of the scheduled job, the schedule, and the handler, the latter being the function executed on the schedule provided. Deno Cron's schedule uses the Unix cron format and the UTC time zone. Deno Cron handlers can perform actions such as updating state in Deno KV, pinging a website, sending email, initiating a database backup, and calling an API at regular intervals."

"Unlike cron jobs on Unix and Linux, Deno Cron executions do not overlap. Hence, if an operator schedules a job to run every 10 minutes but the task takes 30 minutes, Deno Cron automatically skips the next scheduled run until the task is finished. Overlapping cron jobs can lead to unintended issues and require extra logic to avoid, Deno Land said; Deno Deno Cron sidesteps that. Deno Land also is working to support a JavaScript-friendly API to specify the cron schedule."

Deno Land introduced Deno Cron, available behind the --unstable flag in Deno 1.38. Deno.cron() accepts a job name, a Unix-cron-formatted schedule (UTC time zone), and a handler function executed on the schedule. Handlers can update Deno KV, ping websites, send email, initiate backups, or call APIs. Deno Cron prevents overlapping executions by skipping runs while a previous run is still active. Deno Land is working on a JavaScript-friendly API for specifying schedules. On Deno Deploy, cron jobs are detected and managed automatically so jobs run without a web server or continuous requests to keep an isolate alive. The feature aims to reduce boilerplate and simplify scheduled task management.

Read at InfoWorld