4 ms·
I've been using sidekiq (paid, free) for years, the next app (mostly rails apps, but not exclusively) I implement background processing probably will not includ
by deedubaya 5y ago
I've been using sidekiq (paid, free) for years, the next app (mostly rails apps, but not exclusively) I implement background processing probably will not include it.
Reasons to avoid Sidekiq not mentioned:
- Sidekiq does not implement all of or discourages use of activejob abstractions (retry_on, globalid for example)
- Paid support can be curt, hostile, or down-right "works on my machine, sorry!"
- Sidekiq's better performance has never materially mattered for my applications; they're almost always waiting on IO from the db or some net connection.
- mperham 5y agoI'm sorry if any of our previous interactions were less than professional. I often answer support queries from my phone when out and about, so tossing off a curt, one sentence reply will happen. I generally get multiple app issues per day so I can't afford to reproduce every one: just yesterday I asked a customer to provide a reproduction, they worked on it and found the issue was in another gem their app used. At my scale with ~2000 customers, this happens almost every day.