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.