1. 26
  1. 4

    Yet another reason I’m excited about our (in-progress) move from Resque to Sidekiq at $WORK. We get to support an independent developer.

    1. 3

      I’ve used Sidekiq at several jobs and it is just amazing. I remember Delayed::Job. Convinced my current company to upgrade to Sidekiq Pro to get us access to more of its features. :)

      1. 2

        Nice piece of work, Sidekiq is my default go to background worker.

        1. 2

          Congratulations!

          I’ve never been invested in the Ruby world but at the time (2006-2013ish) I was doing PHP and we had Gearman as the de-facto standard for this, also with varying degrees of alternatives and self-built mysql queues. I think the main difference was PHP’s request model, that’s why this was separate from the beginning versus (please correct me if I’m wrong) with Ruby (or Rails) handling a HTTP request, Ruby is not shut down completely (php-fcgi did this later, but I’m talking originally, mod_php).

          Would be interesting to compare the timelines here, but as I’ve just been a user I don’t have any proper milestones memorized…

          1. 1

            Congratulations on the great milestone! It’s nice to see that you’ve managed to be commercially successful with Sidekiq, while staying an independent OSS hacker.

            I’ve been a Sidekiq user since day 1 and I worked on adopting Sidekiq in two different companies. I still remember how painful the second migration was for one of the projects, because the code there relied in some places on the db transactions in DelayedJob.

            It was also amusing to see that a good recipe to become a tech billionaire is to write a Ruby background job processor. :D