InCodeToDeploybyRaza Hussain·Oct 24Rails Background Jobs: Idempotency, Retries, and Duplicate WorkWhy do Rails background jobs run more than once?A response icon1A response icon1
InAWS TipbyFarooq Hussain·Oct 17Your Deploys Are Killing Sidekiq Jobs. Here’s the Fix.How a preStop hook, one Unix signal, and the right grace period stopped Kubernetes from killing our long-running Sidekiq jobs in the middle…A response icon2A response icon2
Aryan Deshmukh·Oct 15The Fix That Only Reached Half the ServerWe fixed a config file, restarted the app and watched one feature recover. The other kept failing for a day and a half.A response icon1A response icon1
Nicolas Vandenbogaerde·Oct 2SolidJobs: Building a Ractor-Native Background Job Processor for Ruby 4What happens when a Ruby background job processor is designed around Ractors from the beginning?A response icon1A response icon1
Ed Martins·Oct 2Measuring at-least-once delivery in Sidekiq under real deploy signalsWhat 132 controlled shutdowns reveal about at-least-once delivery, deploys, and the idempotency guards that don’t hold.A response icon1A response icon1
InSnapdocs Product & Engineering BlogbyJohn Langewisch·Sep 21Sidekiq Scheduled Job Deduplication (Without Killing Redis)At Snapdocs, many of our services are Rails applications running Sidekiq to handle asynchronous jobs. As our platform has scaled, our…A response icon1A response icon1
Gabrielras·Aug 26Sidekiq in Production: 10 Failure Modes Real Companies Have HitSidekiq is deceptively simple. `perform_async`, a worker class, done. It works so well in development that most Rails teams never think…A response icon1A response icon1
In2Performant TechbyAdela Duma·Jul 30The Import Overhaul, Part 3: We Stopped Guessing When Imports Were DoneBlack Friday is when product feeds change the most: prices move, SKUs appear and disappear, feeds get bigger, and merchants re-upload more…
InCodeXbyLakhveer Singh Rajput·Jun 12🚀 Ruby on Rails Background Jobs Mastery: The Complete Guide to Asynchronous Processing ⚡“Great applications don’t make users wait. They work smartly in the background.” 💎
Ahmed A. Ibrahim·Jun 7Why You Should Never Share One Redis Instance for Caching and SidekiqA silent configuration mistake that erases background jobs — and how to fix it before it erases yours.
