A more detailed description of last weekend’s massive GCP outage is on the blog - there’s so much I winced at I can’t even highlight specific interesting lines. https://status.cloud.google.com/incident/cloud-networking/19009 … Configuration change. Automation making things worse. And the postmortem isn’t even fully done
-
-
it reads like the deep reaction is "We just need to be a bit smarter, just add another case for this, we can defeat reality", rather than humility in the face of the unpredictable, and embracing simplicity. 4/n
-
I am reminded of the marketing papers that say Spanner gets around the CAP theorem because the network will be close to perfect. https://cloud.google.com/blog/products/gcp/inside-cloud-spanner-and-the-cap-theorem … … I am just going to use my outside voice when I roll my eyes from now on. 5/5
- 1 more reply
New conversation -
-
-
The strong separation between regions is also in place for the AWS teams internally and not just for customers?
-
it is actually much more strong internally than it is for customers
Customers can communicate between regions if they want to, but AWS teams and services can not. It's a hard wall with precious few exceptions, like some controlled asynchronous replication. - 4 more replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Great point. How much damage has been done in the name of making a two step process, a one step process?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.