Asynchronous Workers to the Resque
summary
Shows three concrete patterns: isolating slow ops, pipelining, and periodic maintenance. Uses Resque with a Redis backend and demonstrates worker classes, enqueue calls, and rake tasks plus cron/whenever scheduling; notes Sidekiq and delayed_job as alternatives. Recommends shared‑nothing and idempotent jobs, copying state into Redis to avoid cross‑process locks, and splitting work into small pipeline stages so failures are traceable. Provides runnable code snippets and practical guidance that works in production.
AI-written summary · about
chapters (4)
related talks
35mProcesses and Threads - Resque vs. Sidekiq
35mSidekiq at Gusto: The Parts Where People’s Jaw Drops
28mFair by design: orchestrating background jobs in Ruby
41mInside ActiveJob
27mFrom Resque to SolidQueue - Rethinking our background jobs for...
56mRedis Application Patterns in Rails
55mThe Past, Present and Future of Background Job...
23mLook Ma, No Background Jobs: A Peek into the Async Future