[timtrueman]

I'm excited for that but what I really meant was split/sharded databases, something you need at scale (which Fluther doesn't need...yet). Correct me if I'm wrong but the upcoming multiple database support can't do that.

http://en.wikipedia.org/wiki/Shard_(database_architecture)

What it seems to support is "Database Routers" which let you implement your own sharding. It's not that you can't do it. It's just that it doesn't support sharding out of the box.

I'm more excited for the template performance improvements.

[simonw]

I don't think it's possible for a framework like Django to support sharding out of the box - there are just too many different ways you might want to implement it. Digg shard by date for example, whereas a site like Flickr shards by user. It completely depends on your application. The database router stuff feels to me like the furthest a framework can go - though maybe a bunch of common routing patterns will emerge in the future.

[johnpaulett]

I can't find a reference to it, but I recall one of the developers mentioning that the current multi-db support lays the ground work necessary for sharding.

I would bet that once 1.2 is released at least several reusable apps pop up that implement various sharding/partitioning strategies.

[timtrueman]

That's the sense I get—that they are laying the framework for more advanced database functionality like sharding.