We are going to set this up for our app, however there's a limit to how useful it is when you are reliant on services such as MongoHQ/PubNub (in our case) that are also affected!
Well, it's not going to be cool or best practice to use cloud services for your startup for the next week or two. Fortunately people on HN will then forget until the next AWS outage and your setup will be fine again.
Duplicating across regions is not well supported by AWS unfortunately. Any idea doing that without completely rebuild the infrastructure in an other region?
I assume you are using the AWS dashboard to manually deploy instances and setting them up by hand? First step is to get your infrastucture to the point where it deploys and scales up and down by itself. Once you manage that, moving to or keeping hot spares in another region is pretty easy.
Look into automated deployment tools like Foreman and configuration management tools like Puppet.
We are learning the hard way that the EC2 Availability Zone separation is not enough, and EC2 is lacking some key features offering multi region tools.
Thanks for the hints, I'm going to check them out.
I echo this... although I don't personally use Foreman. You can do scaling type stuff without the tool and I just use POP (plain old puppet). For me personally it took longer to get on the config-management bandwagon but once I did I have never looked back.
Learning to use Puppet, Chef, Salt or similar will only bring benefits!
How would you recommend performing that failover, when Elastic Load Balancers only cover a single region? If you host your own load balancer it'll have to be hosted somewhere, and DNS failover seems unpopular [1].
DNS failover is fine, even if its manually triggered. We are almost two and a half hours into this network event, so even if you set a 5 minute TTL on your records and it takes you 15 minutes to respond, you are still way ahead of the game.
The idea that some DNS resolver somewhere caches records longer than TTL is mostly a myth. This is the case rarely on some mobile networks and networks behind satellite uplinks, but they generally have larger network issues anyway.
I don't think this comparison is reasonable because the size of index at google is much larger than bing's. For some simple just for test queries, bing's results may seem to be better but in the real world a much larger index is much much more important.
I tried Unison before and gave it up. Not because it is not a great software. But because two way sync itself is very dangerous in my eyes. If I made some stupid mistakes in one side, my all data gone.
I've been considering treating each directory as a separate version control target, so that the archive server would never lose anything. I have the same qualms - although so far, Unison has worked perfectly for me, even in cases where in retrospect that surprised me.
Agreed. Tree-style tabs is just too dreamy. Though I do find myself bringing up Chrome for things like Wave, so I have Firefox up for day-to-day research/etc, and Chrome for quick things and high-JS web apps.
