South has existed and has been in wide use for a very long time, so whether or not it's built into Django doesn't really matter that much. As for Node and Go,

South has existed and has been in wide use for a very long time, so whether or not it's built into Django doesn't really matter that much. As for Node and Go, I don't see how they could have One System To Rule Them All – this feels like something you take care of at the ORM or framework level. Now, as to your "is there another way?" – during development of an app that hasn't yet reached production, I still prefer extensively using fixtures and just nuking the database on every change, then loading the fixtures back in. (In Django this is a one-liner on the shell, I suppose it's probably similar in other frameworks.) Faster and really helps with unit testing too.