[hbrundage]

So glad that Mike has set up a sustainable model for building rock solid infrastructure, however:

I can’t stand that you need to pay for a pro license to avoid completely avoidable data loss. Sidekiq doesn’t use RPOPLPUSH for moving jobs around until you start paying — doing the exact same thing with a different, more correct command. No new infrastructure or configuration is needed. To me this feels sketchy and like a betrayal of the pro-version business model — willfully introducing data loss in order to drive upgrades instead of just removing capabilities or features.

[brightball]

This touches on one of my favorite things about Ruby as a language. The functionality you're asking for becomes pretty easy to monkey patch in yourself without breaking your upgrade path or forcing you to maintain a fork.

IMO that easy of tweaking 3rd party libraries is the reason that Ruby's ecosystem is so polished.

[nickjj]

Yeah that is an interesting point.

It's really easy to drop in an initializer, make your patch, let it ride in production for a while and then contribute your patch back to the main project than it is to set up a fork and all of the ceremony involved with keeping it up to date.

It's a good example of removing barriers of entry or an idea of Ruby's "sharp knives". Great for when you need it but can also be a disaster when abused.

[brightball]

Yep. Definitely a great power, great responsibility tool.

It's the one thing that keeps Ruby closer to true Aspect Oriented Programming than any other language (in my experience at least). It's probably the biggest thing that I miss from Ruby when working in other languages, even ones that I love like Elixir.

[grumple]

Sidekiq is open source, so couldn't you or someone else make another gem for the change? I know there are gems already that enable sidekiq to replicate some of the paid or enterprise features without paying for those plans.

[mperham]

This is also the way Resque does it still today: LPOP. Sidekiq OSS just offers parity with Resque, it never tried to solve this problem.

[senotrusov]

It surprises me that it is a problem that needs to be solved, and not just a way it should be done from day one. Back in 2011 I wrote a small ruby class that interacts with redis and provides me a reliable method to consume messages from queue.

Back than I just read the redis docs, understands that BRPOPLPUSH is the right method to call, and made a few ruby functions to do so, you could see it here [1], they are plain and simple.

From my perspective, it's just feature starving OSS part, to push customers towards the paid solution.

[1]: https://github.com/senotrusov/redis-call/blob/master/lib/red...

[hbrundage]

I mean, it’s also a bug with Resque? Resque predates the introduction of the new command in Redis and hasn’t really been maintained since. “My software is as buggy as 10 year old software unless you pay” seems pretty sketchy to me!