Designing a system which scales to a high number of requests isn't critical for most applications, but you'll never know that it was important until after the fact, so it's worth putting some thought into ensuring your architecture can grow with your success.
When I develop with Django I'm constantly searching documentation, trying to figure out new modules and generally looking for answers to new problems as they arise. Today I'm introducing a new project, Findjango, which hopes to being a valuable resource for searching on Django-related topics.
One of the most common quickie projects on the web is to screenscrape a website and play around with its data. These projects are a lot of fun, and can allow for inventive mashups, but often the screepscraping scripts cause unnecessary load on the site's servers due to inconsiderate technique. This is an introduction to the art of compassionate screenscraping.
A look at how to manage deployment complexity with Django using Fabric. Something of a continuation on the post from yesterday.
Moving along in the Two-Faced-Django series, we look at using JQuery for Ajax in the webapp portion of our program.
Digg's fourth version isn't running anymore, but was an interesting system to work on. This article describes the system architecture, as well as the context behind those choices, and will hopefully be an interesting read for those scaling engineering teams and systems.
Luke and I competed in DjangoDash a few weeks ago, and hey, we actually finished a site.
A rather rough and tumble walkthrough for using Django and JQuery to make autocomplete input fields.
All Rights Reserved, Will Larson 2007 - 2013.