tokio-cron-scheduler
Schedule tasks on Tokio using cron-like annotation (by mvniekerk)
tokio-cron-schedule
By mvniekerk
tokio-cron-scheduler | tokio-cron-schedule | |
---|---|---|
8 | 1 | |
415 | - | |
- | - | |
6.3 | - | |
20 days ago | - | |
Rust | ||
Apache License 2.0 | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tokio-cron-scheduler
Posts with mentions or reviews of tokio-cron-scheduler.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-17.
-
Q3 2023 update - Notifications
As I previously covered in my “Building a scheduler for a Rust application” post, I rely on Tokio Cron Scheduler for various routine background tasks, and one such task runs every 30 seconds (although the default value, it's configurable). This task checks if there are any pending notifications ready for dispatch. Fortunately, the extra 30-second delay doesn't significantly impact my use cases, but it allows me to manage the load more effectively. This approach works equally well for both near-real-time notifications and those scheduled for future delivery.
-
Tokio async / sync bridging causes block
Am I missing something fundemental here? This came from a bug report.The code in question:
-
tokio-cron-scheduler - PostgreSQL / Nats persistent storage (0.6.0)
Release notes here.
- tokio-cron-scheduler Start of persistent job storage (0.6.0-beta.1)
- tokio-cron-scheduler 0.5 - shutdown hooks and ctrl+c signal handling
-
tokio-cron-scheduler v0.4
Release notes here: https://github.com/mvniekerk/tokio-cron-scheduler/releases/tag/0.4
-
Scheduled background task using database in Rocket?
I believe your scheduler is effectively an infinite loop, and from a cursory look tokio_cron_scheduler doesn't gracefully shut down on your behalf. This means by joining you're waiting on an infinite loop, which I don't think should work? Does your program end if you ctrl + c it once?
- v0.3.1 tokio-cron-scheduler - now with async jobs
tokio-cron-schedule
Posts with mentions or reviews of tokio-cron-schedule.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-10.
-
Tokio async / sync bridging causes block
My library tokio-cron-scheduler exposes what seems like a normal sync API but actually inside some of the functions it actually calls tokio::spawn() and returns a signal using std::sync::mpsc::channel().
What are some alternatives?
When comparing tokio-cron-scheduler and tokio-cron-schedule you can also consider the following projects:
lettre - a mailer library for Rust
secutils - Secutils.dev is an open-source, versatile, yet simple security toolbox for engineers and researchers