I'm the primary author SHARQ. Appreciate any feedback..<p>Here is the link to the slides from my PyCon India talk: <a href="https://speakerdeck.com/sandeepraju/sharq-an-open-source-rate-limited-queueing-system-pycon-india-2014" rel="nofollow">https://speakerdeck.com/sandeepraju/sharq-an-open-source-rat...</a><p>Here is our blog announcement: <a href="https://www.plivo.com/blog/sharq-a-flexible-open-source-rate-limited-queuing-system/" rel="nofollow">https://www.plivo.com/blog/sharq-a-flexible-open-source-rate...</a>
This is really cool. Can queues be bounded, as well as rate-limited?<p>(I built my own Redis-backed distributed queue system long ago because I needed bounded queues with backpressure, which no other libraries seemed to offer: <a href="http://github.com/psobot/pressure" rel="nofollow">http://github.com/psobot/pressure</a>)
Seems like the exact same approach and even using the same redis datastrucutres as this talk from RedisConf:<p><a href="http://vimeo.com/52569901" rel="nofollow">http://vimeo.com/52569901</a><p>(Granted, the solution presented here is not open sourced.)
I'm curious as to the author's choice of Redis as opposed to RabbitMQ, or another queue. Redis is problematic when it fails, which makes me question the use of a centralized queue server altogether.