Actually, I should amend this in the interest of not being a hypocrite, seeing as I'm building out a side project right now on top of Cassandra, which is arguab

Actually, I should amend this in the interest of not being a hypocrite, seeing as I'm building out a side project right now on top of Cassandra, which is arguably much slower to get out of the gate with than SQL. But in this case I know from the get-go that I'm going to have massive data on my hands and that I'd have to be sharding a SQL implementation almost immediately, so in the long run it's worth the outlay now. Otherwise, as much as I'd love to toy around with node.js or Tornado or some such, I've got no good excuse and I'm sticking with Django because a.) I'm already familiar with it, b.) batteries are included, and c.) I can move very quickly with it.