Something I keep getting back to is setting up scheduled recurring jobs with Sidekiq, even though some people say it's not the tool for the job, and you might be better of using Cron, I do like the simplicity of using tech that is already there!
With previous versions of Sidekiq, I used Sidetiq, which was super easy to setup. But it does rely on Celluloid, and that is one of the things that is removed in sidekiq 4. I had to start looking for an alternative.
As it turned out, there are a couple of alternatives. In this article, I want to talk about Sidekiq-cron, since this is the tool I'm currently using on some projects.
This tool has a bit of a confusing name. When I first saw the Github repo I believed it was using Cron, and closed the tab right away (Yeah I know, RTFM). It was when a friend of mine pointed out to me that it was not using Cron in any way but just the syntax; it got back my interest!
- Getting it up and running is super simple
- It has a web interface that hooks into the Sidekiq-web dashboard
- You can use YAML for scheduling
- It is compatible with ActiveJob
- If you're using a web server like Unicorn you may run into problems with forking processes.
Getting it up and running
First you need to add the gem to your gemfile:
For this example, I'll be using the following job with the name ExampleJob
Then you need to create your first recurring job, which can be done in two different ways, lets first take a look at the "easiest" way. Which is manually scheduling them:
You can, for example, create an initializer called config/initializers/scheduled_jobs.rb and add a few lines of job creation in there. The downside of this, you have to manually make sure old scheduled jobs are removed before adding new ones.
However, there is another way! You can also load all the scheduled jobs from a YAML file, and it will take care of removed and unique jobs!
You still need to create an initializer
Then we need to create the sidekiq_schedule.yml file:
When you now start your rails app, sidekiq-cron will check what jobs are currently scheduled, and if needed add jobs. Because we used load_from_hash! (With a bang) in the initializer, all jobs that are scheduled but not present in the YAML file will be removed.
Getting the web UI to work
If you're using Sidekiq's web UI, you can also leverage a nice web UI to see what jobs are being scheduled, you can enable this by adding require 'sidekiq/cron/web' after require 'sidekiq/web'