AWS re:Invent 2014: AWS Innovation at Scale with James Hamilton (SPOT301)
Amazon Web Services2 HN recommenders · recommended in 2 months, 2014-2020
70K views · 11 years ago · talk · dated
James Hamilton, AWS VP and distinguished engineer, gives an insider view of the innovations behind the AWS cloud at re:Invent 2014. He covers custom hardware, networking, regions and availability zones, and infrastructure at scale.
HN points to it as an authoritative overview of AWS infrastructure, including what AZs and regions really mean.
1:33:27AWS re:Invent 2016: Tuesday Night Live with James Hamilton
Amazon Web Services
133K views • 9 years ago
46:15AWS re:Invent 2014 | (SPOT302) Under the Covers of AWS: Its Core Distributed Systems
Amazon Web Services
10K views • 11 years ago
28:31Velocity 2010: James Hamilton, "Datacenter Infrastructure Innovation"
O'Reilly
9K views • 16 years ago
53:43AWS re:Invent 2018: Amazon DynamoDB Under the Hood: How We Built a Hyper-Scale Database (DAT321)
Amazon Web Services
112K views • 7 years ago
59:13AWS re:Invent 2018: [REPEAT 1] A Serverless Journey: AWS Lambda Under the Hood (SRV409-R1)
Amazon Web Services
72K views • 7 years ago
42:26AWS re:Invent 2015 | (NET403) Another Day, Another Billion Packets
Amazon Web Services
55K views • 11 years ago
55:44AWS re:Invent 2018: How AWS Minimizes the Blast Radius of Failures (ARC338)
Amazon Web Services
37K views • 7 years ago
52:41Seattle Conference on Scalability: YouTube Scalability
Google TechTalks
30K views • 19 years ago
28:21Velocity 2012: Richard Cook, "How Complex Systems Fail"
O'Reilly
60K views • 14 years ago
59:13AWS re:Invent 2019: [REPEAT 1] Amazon DynamoDB deep dive: Advanced design patterns (DAT403-R1)
AWS Events
115K views • 6 years ago
5:28Inside a Google data center
Google Workspace
22.6M views • 11 years ago
1:05:06AWS re:Invent 2018: Powering Next-Gen EC2 Instances: Deep Dive into the Nitro System (CMP303-R1)
Amazon Web Services
57K views • 7 years ago
53:14Mastering Chaos - A Netflix Guide to Microservices
InfoQ
2.3M views • 9 years ago
1:22:45Building Software Systems At Google and Lessons Learned
Stanford
257K views • 15 years ago
1:10:23"Systems that run forever self-heal and scale" by Joe Armstrong (2013)
Strange Loop Conference
85K views • 5 years ago
59:56AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401)
Amazon Web Services
468K views • 7 years ago
47:18OpenFlow @ Google - Urs Hoelzle, Google
Open Networking Summit
47K views • 14 years ago
1:08:17How We've Scaled Dropbox
Stanford
372K views • 14 years ago
1:14:19NYC Tech Talk Series: How Google Backs Up the Internet
Google TechTalks
41K views • 12 years ago
7:06Putting Google's Network to work for You
Google for Developers
23K views • 12 years ago
6 comments from Hacker News
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), ▶ this 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
▶ this 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 gives a good talk that goes over networking (and more). This is it from reinvent 2014. ▶ this video
Around about here in the talk: ▶ this video James Hamilton talks precisely what the definitions of AZs and regions are :)
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: ▶ this video The scale at FB means they're probably saving hundreds of millions doing this.
> 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: ▶ this video