7 engineers on Hacker News describe using Resque first-hand: 2 endorse it, 2 regret it, 0 are mixed.
“We use (Resque/Jesque) redis-backed queues extensively in our applications/APIs for interprocess communication”
endorse · production · bhz · 2014-11-19 · source ↗ · wrong label?“we switched from Resque because of the awesomeness of only enqueuing jobs after a transaction is committed!”
regret · production · ukd1 · 2014-04-17 · source ↗ · wrong label?“There was resque and then there was sidekiq.”
regret · production · andmarios · 2013-10-05 · source ↗ · wrong label?“We're using a combo of the PHP version and the Ruby version and it's been working great for us”
endorse · production · andrewjshults · 2011-06-26 · source ↗ · wrong label?“I've been using god to manage unicorn and delayed_job/resque processes in recent years.”
neutral · production · pjungwir · 2015-06-28 · source ↗ · wrong label?“We replaced resque with sidekick.”
neutral · production · sytse · 2013-03-22 · source ↗ · wrong label?“the workers didn't really fail in Resque, just failed to do their job”
neutral · production · pimeys · 2011-12-18 · source ↗ · wrong label?