ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAFAGAHAIAJAKALAM
1
systemrails instance per runcan run standalone from background job processoreasily invoke ruby code without clumsy prefix, quoting, etc.jobs are defined as ruby code, not stringsjobs and schedules are defined in different placesschedule is defined in codebasejobs run in rails executorcan run jobs in parallelEasily provide an error handlerEasily run rake tasks within persistent rails instanceEasily run commandline processesrails onlybefore and after callbacksaround callbacksJob must be defined as an ActiveJobjob definitions in databaseWeb UIupdatedlines of code
cloc --exclude-lang="Text,Markdown"
costnotessyntax supported [this column is incomplete]
2
ruby-clocknoyesyesyesnoyesyesyesyesyesyesnoyesyesnonono2022153cron, period, specific time
3
clockworknoyesyesno [sort of]no [sort of]yesnoyes [not by default]yesno?no?no?yesnonoyesno20211,706https://github.com/Rykian/clockwork/issues
https://github.com/Rykian/clockwork/pulls
• Betterment fork: https://github.com/Betterment/clockwork
period, specific time
4
crononoyesyesyesyesyesnoyesnono?no?yesnonononoyes20221,597https://github.com/plashchynski/crono/issues
5
sidekiq-schedulernono https://github.com/moove-it/sidekiq-scheduler/issues?q=independentyesyesyesyesyesyesno?no?nononoyesnoyes20223,147cron, period, specific time
6
sidekiq-cronnonoyesyesyesyesyesyesno?no?nononoyesnoyes20222,576cron
7
sidecloqnonoyesyesyesyesyesyesno?no?nononoyesnoyes20191,069
8
mini_schedulernonoyesyesnoyesyesyesyesno?no?no?nonoyesnoyes20221,371
9
sidekiq enterprisenonoyesyesyes?yesyesyesno?no?nononoyesnoyes?ongoing$230/monthhttps://github.com/mperham/sidekiq/wiki/Ent-Periodic-Jobs

also get other features of Sidekiq Pro+Enterprise https://sidekiq.org
10
GoodJob cronnonononoyesyesyesyesyes?no?noyesno (can define for ActiveJob, but can't define only for cron jobs)no (can define for ActiveJob, but can't define only for cron jobs)yesnoyesongoingGoodJob is an awesome background job processor, this matrix is only comparing its cron capabilities. GoodJob and ruby-clock are a great pair, and also Ben is awesome!uses fugit, so probably supports everything
11
heroku scheduleryes [but each job gets its own instance, so it's a different resource problem]yesnonoyesnoyesyesnono?no?nonononoyes [functionally]noongoing
12
*nix cronyesyesnonoyesnoyesyesnono?no?nonononononoongoing
13
wheneveryesyesnonoyesyesyesyesnono?no?nononononono2020
14
perfectschedyes?yes?nono?no?nono20182,252claims "one-at-least-once" behavior but doesn't really describe the criteria/thresholds (if a 1pm job is missed because of a restart and server comes back at 1:02, does something special happen?)
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100