Happy 6th Birthday, Sidekiq
Six years ago I shipped Sidekiq v0.5.0 and changed my life. I talked to some developers recently:
“I had been working in Go for a while but I kept coming back to Ruby because Sidekiq makes everything so fast and easy to scale.”
This is my recipe for success. Sell a product developers want because it makes their job so much easier. You don’t need a sales force when developers evangelize your product to every new company they join.
My favorite quote from this AMA (with which I wholeheartedly agree) is in regards to Sidekiq: “... rarely does infrastructure so keenly understand what developers, infrastructure engineers, and operators will want out of it.” @mperham https://t.co/RCdG9gwtDV— John K Sawers (@johnksawers) February 3, 2018
2017 revenue was right on target, about 40% higher YoY. Nice, steady organic growth with little marketing on my part. Why burn yourself out chasing arbitrary growth targets from investors? Profitable? Yes. Growing? Yes. Irie, mon.
Today is a BIG DAY!
I’m shipping several releases today:
- Sidekiq 5.1 now has global job death handlers and enables the ActiveRecord query cache by default. Changes
- Sidekiq Pro 4.0 removes deprecated APIs and adds a new experimental feature: batch death. Now if a batch job dies, it marks the entire batch as dead also (since it will never succeed). New APIs allow you to enumerate dead Batches. Feedback is requested here, is it useful? What further refinements would you like to see? Pro Changes
- Sidekiq Enterprise 1.7 adds support for long-running jobs and rolling restarts. Signal USR2 and a Sidekiq process will gracefully exit once all jobs are complete, even if those jobs take hours to complete. This has been a hugely requested feature and it took me a while to figure out how to implement it. Ent Changes
Gotta have it?
Purchase Sidekiq Pro or Sidekiq Enterprise at sidekiq.org.
One of my goals for this year is to slow the rate of releases. There were 12 Sidekiq releases last year but it’s been 4 months since Sidekiq 5.0.5 was released. Ideally I want quarterly maintenance releases.
Lately my biggest problem has been Gmail’s Spam folder. For the last month or two, a very high percentage of customer receipts and welcome emails are winding up in the Spam folder for some reason, despite me sending a very low daily volume from my own email account. I can’t explain it or debug it and feel pretty powerless. Any email delivery wizards have ideas? My email is in the footer.
I also introduced Faktory last year. This is the first step in my long-term plan to bring Sidekiq goodness to all programming languages. I’ll be working on Faktory Enterprise over the next few months and hopefully have it for sale by the end of 2018.
Many, many people have asked me questions about sustainable open source and following a similar path with their project. The Indiehackers interview I did a year ago proved extremely popular and resonanated with many people. Want to discuss more, ask questions? Got an open source project you want to make sustainable? Stop by my weekly Happy Hour and let’s chat.