Wow, that kind of sucks for them. I hope they consider prioritizing some kind of geographic replication after the storm is done. It adds cost and complexity (which slows down development, too), but seems like a good tradeoff when you have customers depending on it.
The geographic load balancing side is basically a solved problem (although you don't want to use only DNS-based load balancing like Route53 in most cases), but the hard part is wide area replication of databases for hot failover.
It's pretty easy to do failover if you'll accept a 5-10 minute outage, though.
The geographic load balancing side is basically a solved problem (although you don't want to use only DNS-based load balancing like Route53 in most cases), but the hard part is wide area replication of databases for hot failover.
It's pretty easy to do failover if you'll accept a 5-10 minute outage, though.