AWS re:Invent 2014: AWS Innovation at Scale with James Hamilton (SPOT301)

> This suggests to me that running distributed databases in multiple AZ's has almost no latency penalty (e.g. you won't even paying eventual consistency / replication lag taxes that you might think are a danger). Yes, Hamilton points that out in his talk: [VIDEO]

This looks great. They also have the advantage that James Hamilton mentioned AMZ got from building their own hardware - the get to do a cleansheet s/w design and not have to support all the gazillion options that Cisco does. The talk was on HN a little while ago, worth watching: [VIDEO] The scale at FB means they're probably saving hundreds of millions doing this.

Around about here in the talk: [VIDEO] James Hamilton talks precisely what the definitions of AZs and regions are :)

James Hamilton gives a good talk that goes over networking (and more). This is it from reinvent 2014. [VIDEO]

[VIDEO] I think this is the right talk by him, but there's one where he implies some differences. For instance, that because they can promise exact temperature ranges they can clock them differently. My guess is same fab, just binned differently, or maybe different packaging.

James Hamilton [0][1] and others [2][3][4] have given pretty good overview over the years of the AWS infrastructure. [0] AWS Innovation at Scale (2014), [VIDEO] [1] Tuesday Night Live (2016), [LINK] [2] Operation of the AWS Global Network (2019), [LINK] [3] Foundations of AWS Infrastructure (2018), [LINK] [4] Exploring the AWS Global Network (2018), [LINK]