Re:Celery, non-blocking code and quest against coroutines
by brianwawok on Thursday June 09, 2016 @01:08PM
(#11870703)
You could totally do concurrency through Reddis or something super lightweight right on your webserver... could make sense. Really seems better to throw your task back to the backend pool though, and let a web request finish.
In effect, you sorta get concurrency (assuming multiple workers are processing jobs).
Or does Celery also provide a way to do threading without using a backend service (e.g RabbitMQ, beanstalkd, sqs)?
Basically, I'm confused.