3 ms·
An Introduction to Sidekiq for Ruby on Rails
- Justsignedup 3y agoDoesn't talk about very common pitfalls that every sidekiq user forgets initially - - retries are bad unless you intentionally want them due to self correcting reasons. Example being retrying an email send due to an http 500 response. And we want those limited, not an unlimited retry that can retry up to a month later. In any case, this doesn't feel like it's much of an addition past sidekiqs own docs. Edit: I definitely didn't intend to make this sound insulting but I realize I did, so I will call myself out on it. The criticisms I have are: 1) note the pitfalls of retries as they are defaulted in sidekiq and some good basic patterns to suggest to devs new to sidekiq reading your blogpost 2) I believe action mailer has an automated mail_later method that would allow you to shortcut the need to create custom jobs. So would be nice to have in there. 3) I suggest showing the two configurations for sidekiq, 1 being the dev setup, and 1 being the env-based setup (which probably should be the dev setup anyways) so that the code can be deployable too.
- mperham 3y agoGood overview! As of Sidekiq 6.3.0, the `Sidekiq::Worker` module is deprecated in favor of `Sidekiq::Job`. I'd suggest you update the blog post wording to reflect modern usage. https://www.mikeperham.com/2021/11/07/whats-new-in-sidekiq-6.3/ https://www.mikeperham.com/2021/11/07/whats-new-in-sidekiq-6...
- unripe_syntax 3y agoThanks for flagging! We've updated the post accordingly.