Question

I know (but I do not understand) that Celery can use Beanstalk as delivery mechanism.

From the Beanstalkd Homepage

"Beanstalk is a simple, fast work queue."

From the Celery Homepage

"It’s a task queue with focus on real-time processing, while also supporting task scheduling."

That seems pretty similar to me. So, why would I choose Celery instead of plain beanstalk? Or why would I choose beanstalk instead of full-grown Celery?

I would like to add a task/work queue to my webapp, but I am not sure which way to go.

Was it helpful?

Solution

Here is the relevant discussion in the Celery mailing list

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top