A couple of days ago I held a presentation about Sidekiq's internals at a local Ruby meetup.

The fact that I didn't know how exactly Sidekiq worked always bugged me. I wanted to know more about how it queues and schedules jobs, so I dug around its source code until I found out. It turns out it's designed very elegantly and relies on Redis for queuing and scheduling as much as it can (which is a good thing - because Redis is awesome).

I'm gonna cover what I found out in detail in one of future blog posts and just post the slides here for now.

The slides were build using remark.js and are hosted locally.