Hacker News new | past | comments | ask | show | jobs | submit login

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.



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...


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!




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: