Good question - I've been using Beanstalk to handle hundreds of thousands of worker transactions per second for years.

I suppose development on it has slowed to a crawl so it's no longer "actively" supported.

Both are very equal it seems, with only some minor differences. Disque isn't used in production systems yet so most likely the real comparisons will arrive when Disque is more mature.

Some key differences are that beanstalkd offers (feature wise):

1. Bury / kick 2. Priorities 3. Designed for speed

And Disque:

1. Designed for HA, scalable, distributed 2. Fault tolerant 3. Peek to multiple jobs

With the amount of momentum behind Redis and the fairly unknown beanstalkd, I guess Disque will gain popularity quite soon.

BeanstalkD doesn't have the HA built into it and you have to work around that if you want HA.

https://github.com/kr/beanstalkd/wiki/faq#does-beanstalk-inh...