Here’s a compelling case against using Sidekiq, even though it’s often praised for being 15 times faster than Solid Queue or ActiveJob when processing an empty job. While that speed sounds impressive, it’s not the whole story—and there are good reasons to think twice before choosing it.

When rate limiting jobs, I use a simple redis rate limit lua script that I posted here: https://mhenrixon.com/articles/client-side-rate-limiter , and I also use a similar scheduler to spread the jobs out. This is how I do it

Redis default configuration needs to change for a sidekiq queue backend. This is how you do it right!

Sometimes you have to get ahead of things. Rate limits suck but are there for a reason, waiting until the API you are calling raises a rate limit error is bad, really bad. This is how you get ahead and prevent the external API from raising rate limit errors.