igorzi
Re:Deno Cron
on Wednesday November 29, 2023 @04:38PM (#38465684)
If you need to manipulate state - you should use Deno KV or some other persistent database. V8 isolates are created on-demand to handle Deno.cron and Deno.serve requests, potentially in different regions. You should not make assumptions that the same isolate will be used to handle all requests.
This is being worked on: https://github.com/denoland/deno/issues/21122. Should be available with the next Deno release.
Yes, we're anticipating more spiky workloads because of this. Deno Deploy is already designed to handle spikes, but we also have a few additional mitigations in place for Cron. For example, we will limit concurrent dispatches for the same project/user/organization, which may slightly delay the execution of specific cron tasks.
We're gathering more feedback for supporting self-hosted cron environment. Can you describe how you would use it?
Not currently, but this is on the roadmap