Recurring Background Jobs with Sidekiq-scheduler
summary
sidekiq-scheduler actually adds recurring job scheduling to Sidekiq and uses Rufus-Scheduler to get second-level resolution, supporting cron, every, at and in types. Cron and At schedules deduplicate across multiple schedulers; Every and In still need work for multi‑node safety. Demo shows a job that runs every minute to auto-close marked repo issues and it works. Project has 43 contributors and allocates six hours per week for maintenance, and plans to stop polluting global Sidekiq config.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:11USE CASES
- 4:18GETTING STARTED
- 5:50SCHEDULING TYPES
- 8:14THE CHALLENGE OF MULTIPLE INSTANCES
- 13:32Extension's web app
- 15:30FEEDBACK & COLLABORATION
related talks
35mSidekiq at Gusto: The Parts Where People’s Jaw Drops
39mAsynchronous Workers to the Resque
55mThe Past, Present and Future of Background Job...
35mProcesses and Threads - Resque vs. Sidekiq
41mInside ActiveJob
28mFair by design: orchestrating background jobs in Ruby
32mGrowing Your Background Job Knowledge
11mRunning Jobs at Scale