Re: Example uses of Celery

Celery is great for doing work asynchronously.  In web contexts asynchronous work is useful since doing heavy lifting while the user is waiting on your response doesn't lead to high perceived performance.

In non-web contexts, it is useful for submitting work into "the system" and having workers churn through it task, after task.  This solves many of the annoying (and unproductive) patterns developers who need to across systems to talk with each other.  Instead of submitting the call to the other web service directly, you give it to the broker, who delivers it to the workers for you.  This keeps programmers from having to worry about overrunning the other worker with requests or situations where the other service is unreliable or experiences an outage.  If the third party service did go down and the workers die for any reason the broker will continue to deliver the messages once the workers come online.  Thus, Celery is a great way to increase reliability while making things simpler for the programmer.  These are high level observations...

Celery can seem Django specific because early on there was a dependency on Django (even if you weren't using Django).  There is also really excellent integration with celery through the django-celery project.

Brian

On Mon, May 23, 2011 at 9:49 PM, br <roberts81@gmail.com> wrote:

I understand a lot of production systems use celery and/or cron to
automate task queues and/or scheduling.  I am just getting involved in
a startup and will be the go-to guy for tech stuff and am interested
in what types of tasks people use Celery (or a celery-like platform)
for so that when similar types of things come up in my company, I'll
think of it first.    I've read through the manuals a bit, but its
mostly technical and implementations.  I'd like some examples to
analogize to and then I can apply the code  when stuff comes up.    I
realize Celery isn't a django-specific tool, but it seems to go hand
and hand a lot of times and we are building our platform in django.

Thanks,

br

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
Brian Bouterse
ITng Services

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.