Thursday 4th October, 2012
2:00pm to 2:40pm
Any useful web application contains some actions that are too slow to run inside a web request. Common examples include sending email, processing uploaded files, or running complex database queries. Using a job queue to do this work in the background is an easy way to get huge performance improvements, but is also an easy way to create huge engineering and user experience headaches.
In this session we’ll take a look at the different ways of running tasks offline, and help you understand which one is right for your application. We’ll also cover:
Trying to make @slackhq even better. Previously at @typekit, @flickr, @bbc and some other stuff. bio from Twitter
Sign in to add slides, notes or videos to this session