Friday, May 27, 2016
I second this. Sidekiq (especially version 4) is amazing. Clockwork is great too for scheduling recurring jobs. There was a sidetiq which would schedule sidekiq jobs however it is not actively being developed and lacks sidekiq 3.5.1 and 4.0 support. You have to use a version that's back ported with Celluloid 0.17.1 (I think that's the version number). I'd stay away from sidetiq and focus on clockwork and sidekiq itself.
If sidekiq becomes too much technical debt and you need something that just works and is easy to use minus the reds dependency and monitoring with bluepill or god, I recommend sucker_punch https://github.com/brandonhilkert/sucker_punch. It does not have job re-enqueing or persistence past the memory space (if you restart your app server (puma/passenger/unicorn) you lose your pending jobs. But it's a great little gem and I use it for lots of small projects where sidekiq is overkill.
On May 27, 2016, at 3:50 AM, Saurav <prionko@gmail.com> wrote:Checkout both https://github.com/tomykaira/clockwork and https://github.com/mperham/sidekiqI have used both of them for scheduling different kind of background jobs.Saurav
On Thursday, 26 May 2016 20:07:26 UTC+5:30, der_tom wrote:which toll should i use? my task needs to be run after 1 hour or other time unit afte r the record has been created.thxtom--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/87c2cce7-082b-44c4-83aa-26389820fec9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment