> and some small but annoying bugs while testing
Do you recall any details?
Appreciate you trying TaskTiger, even if you've moved on since!
It came down to I like the features of RabbitMQ:
* RabbitMQ scales messages without needing tons of RAM * I don't have to decide between not persisting messages to disk with Redis vs only using half the machine's RAM [1] * Queue and task visibility is better in RabbitMQ * Support for purging all tasks in a queue * Tasktiger had lower throughput than Celery and Dramatiq, maybe needs lazy-forking?
Things I did like about Tasktiger: * no feature bloat and it's possible to actually read it's source code[2].
[1]: To enable persisting to disk (Redis fork + save snapshotting) you must limit Redis to only using half the available RAM on a machine.
[2]: Celery is split up into multiple convoluted, bloated, difficult to read repos.
Especially never had problems with zombie workers. That wouldn't be a problem with your choice of queue library, more an infra problem.