Growing Your Background Job Knowledge
summary
Shows a concrete before/after: a controller calling a service that sleeps five seconds and blocks the request, then moves that work to a background queue and calls perform_later so the page returns immediately. Uses Rails Active Job with adapters like Sidekiq, Resque, Delayed Job or the in‑memory async backend. Highlights global serialization via global IDs, locale preservation, callbacks, retry/backoff and rescue_from, and the real pitfall that in‑memory jobs die on Heroku dyno restarts.
AI-written summary · about
chapters (6)
- 0:00Background jobs basics
- 3:11Blocking request problem
- 9:32Background jobs and async
- 14:02Rails Active Job solution
- 21:11Active Job features
- 30:23Key takeaways
related talks
01h 06mThe Background on Background Tasks in .NET 6
59mThe Background on Background Tasks in .NET Core
11mRunning Jobs at Scale
35mSidekiq at Gusto: The Parts Where People’s Jaw Drops
32mZero Downtime Deploys Made Easy
29mServices, Scale, Backgrounding and WTF is going on here?!???
53mMaking tomorrow's code look like today's
51mCode the Future, Now