Don’t use Celery.
It doesn’t solve a single problem that a set of bare queue consumers can’t resolve.
It doesn’t solve a single problem that a set of bare queue consumers can’t resolve.
- By default, task IDs are just pickled Python objects - if you want to change the location of a function, it might break; - The whole process appears to be reloaded for each task - any heavy loading ends up being performed on each call; - I couldn't find any "ops" documentation: how does it interact with RabbitMQ? How are deferred tasks implemented? What happens if a node crashes?
Although the API is nice, the product itself seems ill-suited for actual reliable, production use — at that point, it's sometimes easier to just deploy your own minimal API using the serialization format you've chosen to adopt (JSON, Protobuf, ASN.1, … ;)
"It doesn't solve a single problem that a set of queue instances on a single machine solve. Who needs any resilience?"
Weird take, that is provably incorrect and wrong.
No thanks.