1. Expensive tasks that you don't want the user waiting on. For
example: sending messages;
we have triggers for SMS, Email and iPhone APN messages. I don't
want the request/response
waiting around while I do all of that.
2. Tasks that could fail and need to be retried. For example:
updating settings on
the backend, you don't need complicated retry logic.
3. Replacement for cron. The biggest issue with cron is that it is
single server.
Once I switched to celery I don't care which processing server
launches the task.
On May 23, 9:49 pm, br <robert...@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.
No comments:
Post a Comment