que-scheduler
A lightweight cron scheduler for the async job worker Que (by hlascelles)
Clockwork
A scheduler process to replace cron. (by Rykian)
que-scheduler | Clockwork | |
---|---|---|
1 | 2 | |
112 | 535 | |
- | - | |
8.2 | 0.0 | |
5 days ago | 6 months ago | |
Ruby | Ruby | |
MIT License | MIT License |
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.
que-scheduler
Posts with mentions or reviews of que-scheduler.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-05-03.
-
Ruby Schedulers: Whenever vs Sidekiq Cron vs Sidekiq Scheduler
Do also take into consideration que-scheduler (disclaimer, am author). It is built on top of the robust que async job system.
Clockwork
Posts with mentions or reviews of Clockwork.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-25.
-
Newest way to handle Cron Jobs?
https://github.com/Rykian/clockwork always worked well when I have used it in the past.
-
Any idea how can we convert the string time to utc in ruby.
Unless you have very specific requirements that preclude this, you might want to run this task as a background job (e.g. Sidekiq worker) instead of as a rake task. This is a little bit of an opinion. There isn't one right way (indeed, that's one of the best things about Ruby). But in my career I've usually seen rake tasks used for things that need to be performed infrequently, and not as part of normal system operation. For things that need to be performed at regular intervals, and are part of the normal operation of the app, I usually see them set up as scheduled background jobs. You can use a background job gem (Sidekiq is wildly popular; Resque is another good one) and combine it with a scheduler (I'm personally a fan of the Clockwork gem but there are others out there).
What are some alternatives?
When comparing que-scheduler and Clockwork you can also consider the following projects:
sidekiq-scheduler - Lightweight job scheduler extension for Sidekiq
Whenever - Cron jobs in Ruby
minicron - 🕰️ Monitor your cron jobs
Sidekiq-Cron - Scheduler / Cron for Sidekiq jobs
Montrose - Recurring events library for Ruby. Enumerable recurrence objects and convenient chainable interface.
rufus-scheduler - scheduler for Ruby (at, in, cron and every jobs)
resque-scheduler - A light-weight job scheduling system built on top of Resque
que-scheduler vs sidekiq-scheduler
Clockwork vs Whenever
que-scheduler vs minicron
Clockwork vs Sidekiq-Cron
que-scheduler vs Sidekiq-Cron
Clockwork vs sidekiq-scheduler
que-scheduler vs Montrose
Clockwork vs rufus-scheduler
que-scheduler vs Whenever
Clockwork vs resque-scheduler
que-scheduler vs rufus-scheduler
Clockwork vs minicron