Celery Beat > cron?

[Lemuel Formacil]

Anyone here have experience running scheduled tasks with Celery Beat rather than cron?

I thought yadda-yadda using the right tool for the right job and I should be using cron, but now I want to make all the app's logic and behavior all in the app and I thought about moving the scheduling of the tasks within the app, so I looked into celery beat, and it turns out more people (more like 3 people in stackoverflow) are preferring celery beat over cron.

So, anyone here have experience running tasks via celery beat rather than cron?  Is it up to the...task? (hehehe)  Is it production-grade?  Any warnings, horror stories?


--

Lemuel

[azizmb.in]

I think celery overall is pretty stable, and if you are careful about your configurations (exponential wait between retries, timeouts, good logging and monitoring), it should be a very reliable part of your architecture. I'd used celery beat a long time back on production, but for a medium scale app.

Arguments for celery vs cron for me would be,

1. More encapsulation of the application.
2. Much easier to handle locking, ie, don't run a task if a previous instance of the task is running.
   
3. Support for retry. You can handle retries much more gracefully with celery. With cron, you have to DIY.
   
4. Better tools for monitoring, etc. NewRelic supports celery pretty well.

--
You received this message because you are subscribed to the Google Groups "from mena import python" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python-mena...@googlegroups.com.
To post to this group, send email to pytho...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Abde Sayedna,

Aziz M. Bookwala

Website | Twitter | Github