Hacker News new | ask | show | jobs
by ransom1538 2779 days ago
“2) This issue was global in scope, affecting all of Google's regions. Therefore, in consideration of item 1 above, it was questionable/unpredictable whether or not a user could launch a node pool or even a simple node anywhere in GCP at all.”

Ok. So on aws we were* paying for putting systems across regions, but, honestly I don’t get the point. When an entire region is down what I have noticed is that all things are fucked globally on aws. Feel free to pay double - but it seems* if you are paying that much just pay for an additional cloud provider. Looks like it’s the same deal on GCP.

1 comments

> When an entire region is down what I have noticed is that all things are fucked globally on aws.

Do you have an example on this?

On 17 October, there was a multi-AZ network failure at us-east-1. It only lasted 3m35s, but it was enough that our customers were calling about our site being down.
That's still just one region, unless you were also hosted outside us-east-1.
Just grabbed first article. Example: In this case capitalone went down. I don’t work at capitalone - but I imagine they had their data copied across every region 30 times.

https://www.geekwire.com/2018/widespread-outage-amazon-web-s...

I think you're much too optimistic about capitalone. They probably had a single point of failure, possibly one they didn't realize they had.
CapitalOne is one of the few financial markets firms with open source cloud projects on github. I respect their tech org for that.