2011/5/6 λq <lamb...@gmail.com>: > Hi guys, > > We have a django product running, one of the view is to track each > request of news and write to MySQL, so when user grows the track > read/write became heavy and it may take a while for the user to get a > response. So we are thinking about something like async worker process > to do the MySQL write task but give the client a quick response first. > Something like a Message Queue. What is currently the best practice > for Django 1.2 for these kind of stuff? > > Thanks in advance. > > Regards, > > λq >
The popular response will say 'celery/django-celery'. This works well, but in my mind is more suited to longer running tasks. You may be better suited directly using a MQ directly. I have good results using pika and rabbitmq from django, for when I want more AMQP-like behaviour, rather than 'background task' behaviour. Cheers Tom -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
