My main complaint with celery is its deployment model – it’s a non-trivial amount of operations work to keep the cluster of workers updated as the code evolves. This is in contrast to systems that ship code from the master, where the worker nodes are very dumb.
My other complaint is that the software itself seems to encourage coupling the worker code very tightly with the celery job system, making it difficult to run locally or test. While you can explicitly run a job in the current thread, that falls apart once you do anything interesting with chaining jobs and other fun control flow related operations.
Does Dramatiq solve either of those pain points? As far as I can see in the docs the answer is “no.” I don’t mean to come off sounding like a curmudgeon, it looks like a cool project! I think I just need something fundamentally different.
My main complaint with celery is its deployment model – it’s a non-trivial amount of operations work to keep the cluster of workers updated as the code evolves. This is in contrast to systems that ship code from the master, where the worker nodes are very dumb.
My other complaint is that the software itself seems to encourage coupling the worker code very tightly with the celery job system, making it difficult to run locally or test. While you can explicitly run a job in the current thread, that falls apart once you do anything interesting with chaining jobs and other fun control flow related operations.
Does Dramatiq solve either of those pain points? As far as I can see in the docs the answer is “no.” I don’t mean to come off sounding like a curmudgeon, it looks like a cool project! I think I just need something fundamentally different.