Comments on: Scaling Django to a Global Audience with Playdoh

By: Anderson

Anderson — Fri, 29 Jul 2011 00:14:10 +0000

thanks for your answers Fred =]

By: Fred Wenzel

Fred Wenzel — Fri, 29 Jul 2011 00:02:41 +0000

We’re not using South by default because in the past, we had problems with it being too “smart” and applying migrations differently between our development instances and staging/production servers. We found that the pain of fixing that was much larger than the work it took to just write (or copy-and-paste) a line or two of SQL.

That being said, there’s nothing in Playdoh that would keep you from just using South, and in fact you’re more than welcome to.

As for replication, note that Postgres 9.0 does include “hot” replication out of the box — I haven’t used it before, but I hear it works well.

By: Anderson

Anderson — Thu, 28 Jul 2011 23:56:58 +0000

I didn’t know that mysql has all that built-in.
I was struggling to do a replication on postgres using londiste.

For the migrations question above…there’s a specific reason why you dont use “south”? Because south seems to be the most used app for these migrations on Django.

thanks for your answers and your video =].
I really enjoyed it

By: Moreno Cunha

Moreno Cunha — Thu, 28 Jul 2011 22:07:05 +0000

Very good news! ^-^
I can’t wait to check it out.

By: Fred Wenzel

Fred Wenzel — Thu, 28 Jul 2011 21:37:05 +0000

Rich: By migrations tool you mean the tool we use to do database migrations? We use a very simple tool named “schematic” that keeps track of what “version” your database has and lets you run arbitrary SQL (and lately: Python) files to change your database schema as you go. There are some (short) docs here that might help you, have you seen them? http://playdoh.readthedocs.org/en/latest/migrations.html

By: Fred Wenzel

Fred Wenzel — Thu, 28 Jul 2011 21:34:02 +0000

Anderson: We run most of our websites off MySQL, which has replication functionality built-in. We change the settings so one database considers itself the master, and all others are slaves that replicate from that master database. If the master goes down (luckily, a rare event) one of the slaves can be “promoted” to become a master then.

By: Anderson

Anderson — Thu, 28 Jul 2011 13:30:05 +0000

Thats great. I would love work with you guys in mozilla. Thats definitelly one of my top dream jobs.

I have a question: You said you use at least two DB, one for writing other for reading. Wich tool, or how, you do replication between these databases?

By: Rich

Rich — Thu, 28 Jul 2011 04:55:04 +0000

I’d love a tutorial on how to use your migrations tool!

By: w1sh

w1sh — Wed, 27 Jul 2011 18:41:16 +0000

Awesome video. Awesome project. I can’t wait to dig in.

Thanks Mozilla for leading the way!

By: Mladen

Mladen — Wed, 27 Jul 2011 02:02:30 +0000

Awweesomeee.. will be exploring it in the next few days. This is a very necessary set of tools for anyone working on or learning Django. Thanks for working on this and even more for making it available!