On Oct 13, 2010, at 1:58 PM, Brian Bouterse wrote: > I have found cron to be a poor solution for this although it is tempting > since it is so easy and will get you started right away. What I observe > happens is, basically someone puts the cron job in crontab, and then a lot of > time passes, and folks forget which machine in the cluster is actually in > charge of the cron job. Eventually that machine gets rebuilt or re-deployed, > and then folks wonder why stuff mysteriously stops working. This has > happened at least 3 times over the years at different places I have worked > at. (I'm a site reliability engineer). > > Cron is a fine solution, but it's such a single-point solution that it is > fragile over time because folks forget about it, and it has a single point of > failure. my 2 cents. > > Brian
I've found exactly this to be the case. I'm in the process of eliminating our cron-based activity in favor of a django-celery solution. We have django-celery and RabbitMQ in production and I'm excited about the possibilities. Coincidentally, thanks to Brian for his advice and enthusiasm for these tools when we met at DjangoCon. It's surprisingly easy to get set up with nothing more than the tutorial/into for django-celery. If anyone has problems with it I'd be happy to try to assist. Although getting everything working is fairly easy, in my opinion the docs aren't too clear on how the big picture really works for first-timers. Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
