I'm also in the 'anything but Celery' camp:

https://dramatiq.io/motivation.html

If you're backing onto something like SQS or Rabbit (Redis is a bit trickier), it's not the worst thing to hand-roll either. Then you understand exactly what trade-offs you're making.

I had a good time with dramatiq+apecheduler, much more bare bones and less out of the box, but when something went wrong is was pretty easy to understand and work around.

Dramatiq is great.

For under 1000 messages per second, PostgreSQL is great at queues.

We have transitioned over to Dramatiq.

It has its own set of problems (mostly from starting at the set of "we will remove all of Celery features" and then going from there), in particular its logging policies are extremely frustrating and we have had to work around them. But the code is so simple in general that we get good compensation for that.

I personally would have liked to use dq instead but that's mostly an aesthetics thing.

Beanstalkd?

These comments say better than I can why I like it

https://news.ycombinator.com/item?id=27483167

https://news.ycombinator.com/item?id=24714198

Celery is not a broker daemon, it's an abstraction for them. You can use it with various brokers and some kv databases such as redis.

And yes, celery also supports beanstalk, so it's clearly not an alternative to it

http://docs.celeryproject.org/en/latest/getting-started/brok...

Currently exploring using arq, a successor to rq for my next project.