Sidekiq-Cron VS cloudtasker

sidekiq-cron

this might be useful? https://github.com/ondrejbartas/sidekiq-cron

Depending on how far into the future you're planning to, it could be worth storing the datetime you want it executed on a field like perform_work_at within your database. Then use sidekiq-cron to check a few times a day for if the perform_work_at has passed & the work needs to be done.

The cron job itself was not a huge hassle; the sidekiq-cron gem worked really well for me here to get everything configured in the application.

If what you need is a job (related to application) you can use sidekiq with sidekiq-cron [https://github.com/ondrejbartas/sidekiq-cron] running every x seconds or when a job ends starts a new one.

The Cloudtasker gem automatically adds a duration field on each "Job done" log entry. This value can be used to create a metric on job duration.

TL;DR; It is now possible to use Google Cloud Tasks with Active Job using the cloudtasker gem with the release of v0.11.0. If you intend to deploy your Rails app on Cloud Run, Cloudtasker is the easiest solution to get started with background jobs on Rails.

We just released support for Active Job on cloudtasker, a gem for background jobs using Google Cloud Tasks as a backend.

Let's take a concrete example: background jobs. Should you use ActiveJob, Sidekiq, Resque or Cloudtasker for GCP, it's very common to have jobs defined like this:

Here is the link to the library: https://github.com/keypup-io/cloudtasker

Migrating from Sidekiq to Cloud Tasks using our cloudtasker gem is fairly easy considering they're pretty much using the same syntax. Don't hesitate to ask questions on the cloudtasker project if you need help!