For the SQL datbases they provide a sync service that can replicate your database automatically between different regions (or even a local database).
I have no clue how reliable all of this is, but at least in theory it looks as if it might be quite a bit easier to do full geo replication across different regions on Azure.
Anyone with actual experience?
I think Google Compute Engine does exactly that, with a direct connection between regions so the entire system works as one network. I'm not sure if that will be the case outside the US, though.
The diagrams show two separate masters in different regions with their own slaves, yet DNS is essentially randomly delivering users to each "half". There is no mention of how this is handled, or even that you would have to consider it.
If your application is architected to use SimpleDB, DynamoDB, SQS, or even RDS, these simple "You should have been using Route 53 and multiple regions" articles get increasingly frustrating. Most applications simply aren't elementary enough to fit into that boilerplate structure, and getting around that fact either requires switching away from Amazon's managed database services (lots of money) or writing synchronizing scripts that play nicely with your stack and launching them on additional servers (lots of money and lots of resources).
While ideally I'd like to see Amazon release some sort of feature for multi-region sync, it would be interesting to see how the tried-and-true multi-region businesses have approached this problem.