We've moved discussions to Discord

A Common Heuristic for Choosing Sidekiq or DelayedJob?

Donn Felker
I've been using Sidekiq on another project of mine for years. It has been great and it just works, but it does increase the dependency surface area and processes you need to run. Just more stuff to manage.

DelayedJob works great until you start to need to scale (or need a dashboard). However, it's super simple and easy to just start using very quickly. 

What does everyone use for a heuristic for determining whether you should use DelayedJob or Sidekiq? Or do you always just use one or the other, and why? 

Reason: I'm firing up another project with Jumpstart and originally I chose Sidekiq, but upon further introspection, I'm realizing that I probably don't need that. I'm trying to be pragmatic about it and was wondering what others do when deciding on a background job processor. Thanks!
Donn Felker
I've been using Sidekiq on another project of mine for years. It has been great and it just works, but it does increase the dependency surface area and processes you need to run. Just more stuff to manage.

DelayedJob works great until you start to need to scale (or need a dashboard). However, it's super simple and easy to just start using very quickly. 

What does everyone use for a heuristic for determining whether you should use DelayedJob or Sidekiq? Or do you always just use one or the other, and why? 

Reason: I'm firing up another project with Jumpstart and originally I chose Sidekiq, but upon further introspection, I'm realizing that I probably don't need that. I'm trying to be pragmatic about it and was wondering what others do when deciding on a background job processor. Thanks!
Notifications
You’re not receiving notifications from this thread.
© 2022 Jumpstart Pro by GoRails, LLC