News for hackers. Stuff that matters.
Re:Celery, non-blocking code and quest against coroutines by fideloper on Thursday June 09, 2016 @12:02PM (#11870266)
So if I'm reading this correctly, the author is using a queue system (Celery, presumably with a backend such as RabbitMQ?) to run background jobs, but then waiting for them all to complete before finishing a task.

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.

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.