Show HN: SHARQ – Open Source, Rate-Limited Queuing System

I&#x27;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:&#x2F;&#x2F;speakerdeck.com&#x2F;sandeepraju&#x2F;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:&#x2F;&#x2F;www.plivo.com&#x2F;blog&#x2F;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:&#x2F;&#x2F;github.com&#x2F;psobot&#x2F;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:&#x2F;&#x2F;vimeo.com&#x2F;52569901</a><p>(Granted, the solution presented here is not open sourced.)

I&#x27;m curious as to the author&#x27;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.

Missing Github link: <a href="https://github.com/plivo/sharq-server" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;plivo&#x2F;sharq-server</a>

Looks pretty cool, congrats on the ship!