Here's the list of my issues: https://github.com/closeio/tasktiger/issues?utf8=%E2%9C%93&q=is%3Aissue+author%3Aalanhamlett https://github.com/closeio/tasktiger/

Here's the list of my issues: https://github.com/closeio/tasktiger/issues?utf8=%E2%9C%93&q=is%3Aissue+author%3Aalanhamlett https://github.com/closeio/tasktiger/issues?utf8=%E2%9C%93&q... 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.