Going for a trot on the Django pony
blog.fluther.com
Going for a trot on the Django pony
1–10 of 16 posts
Re: Going for a trot on the Django pony
#2One of the poster's "cons" was lack of support for multiple databases.
Django 1.2 will have support for multiple databases: http://djangoadvent.com/1.2/multiple-database-support/
Re: Going for a trot on the Django pony
#3One of the poster's "cons" was lack of support for multiple databases. Django 1.2 will have support for multiple databases: http://djangoadvent.com/1.2/multiple-database-support/
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.
Re: Going for a trot on the Django pony
#4Split database support is in Django 1.2 (currently in beta), so that's one con to scratch off the list.
Re: Going for a trot on the Django pony
#5One of the poster's "cons" was lack of support for multiple databases. Django 1.2 will have support for multiple databases: http://djangoadvent.com/1.2/multiple-database-support/
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 do…
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.
Re: Going for a trot on the Django pony
#6One of the poster's "cons" was lack of support for multiple databases. Django 1.2 will have support for multiple databases: http://djangoadvent.com/1.2/multiple-database-support/
Also, South was considered for 1.2 but deemed not yet ready: http://code.djangoproject.com/wiki/Version1.2Features#Highly...
Re: Going for a trot on the Django pony
#7A little off-topic, but I love the design and typography on the Fluther blog!
Re: Going for a trot on the Django pony
#8One of the poster's "cons" was lack of support for multiple databases. Django 1.2 will have support for multiple databases: http://djangoadvent.com/1.2/multiple-database-support/
Also, South was considered for 1.2 but deemed not yet ready: http://code.djangoproject.com/wiki/Version1.2Features#Highly...
From personal experience, South is not ready.
I end up spending 10x the effort using it than writing a few custom queries to add columns or drop a table.
Re: Going for a trot on the Django pony
#9One of the poster's "cons" was lack of support for multiple databases. Django 1.2 will have support for multiple databases: http://djangoadvent.com/1.2/multiple-database-support/
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 do…
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.
Re: Going for a trot on the Django pony
#10Earlier quoted context omitted.
Also, South was considered for 1.2 but deemed not yet ready: http://code.djangoproject.com/wiki/Version1.2Features#Highly...
From personal experience, South is not ready. I end up spending 10x the effort using it than writing a few custom queries to add columns or drop a table.
How well would you say you know South?
I felt that way at first but once I got to know South I found it to be much better than custom queries.