3 ms·
Completely agree Several developers like to overengineer and "go for celery" (also applies to other technologies with other uses) even for small things. You d
by raverbashing 7y ago
Completely agree
Several developers like to overengineer and "go for celery" (also applies to other technologies with other uses) even for small things.
You don't need Celery to run a batch job every day for example. Or to even do some parallel processing.
"Oh but python multithreading sucks" do you know when it does not suck? When your thread is waiting on something else. Also there's the multiprocessing module with a lot of "batteries included" for basic use cases.
Not to mention (my biggest pet-peeve of Celery) is that it "forces" you to work with a task queue model. Not a data queue model. Sure, it helps a lot when you need that, but sometimes you just need a queue.