Velocity 2011: Jon Jenkins, "Velocity Culture"
O'ReillyRecommended by 1 HN commenter across 1 month, 2012–2018
talk · intermediate · 2012–2018 on HN
Amazon's Jon Jenkins at Velocity 2011 on how operations can drive revenue and on Amazon's highly available, autonomous architectures. It includes details on deployment frequency and Amazon's move to AWS.
HN commenters cite it as a primary source for facts such as Amazon.com running on AWS and its very frequent deployments.
Up next
10 mo on HNVelocity NY 2013: Richard Cook, "Resilience In Complex Adaptive Systems"
O'Reilly
Recommended 4× on HN · 2017–2021
11 mo on HNDebugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017
GOTO Conferences
Recommended 8× on HN · 2018–2025
9 mo on HNAWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401)
Amazon Web Services
Recommended 12× on HN · 2019–2025
9 mo on HNLiterate Devops with Emacs
Howard Abrams
Recommended 8× on HN · 2015–2025
6 mo on HNContainers From Scratch • Liz Rice • GOTO 2018
GOTO Conferences
Recommended 6× on HN · 2018–2025
6 mo on HNOver 200,000 Servers in One Place! Visiting Hetzner in Falkenstein (Germany)
der8auer EN
Recommended 6× on HN · 2021–2025
5 mo on HNBryan Cantrill from Joyent on Manta: internet-facing object storage facility that features compute
AI Council
Recommended 4× on HN · 2014–2026
6 mo on HNZebras All the Way Down - Bryan Cantrill, Uptime 2017
Code & Supply
Recommended 6× on HN · 2018–2025
5 mo on HNElixirConf 2018 - Docker and OTP Friends or Foes - Daniel Azuma
ElixirConf
Recommended 4× on HN · 2018–2023
6 mo on HNStanford Seminar - The Soul of a New Machine: Rethinking the Computer
Stanford Online
Recommended 3× on HN · 2020–2025
5 mo on HNAWS re:Invent 2016: Tuesday Night Live with James Hamilton
Amazon Web Services
Recommended 5× on HN · 2016–2023
5 mo on HNHow We've Scaled Dropbox
Stanford
Recommended 5× on HN · 2014–2023
5 comments from Hacker News
Amazon describes its internal service architecture here: ▶ this video Services use an internal tool called Apollo to describe the service, deploy it to EC2 VMs, and auto-scale. Apollo inspired AWS CodeDeploy and AWS AutoScaling. Services are reachable via load balancer sets similar to AWS ELB/ALB/NLB. You reach a service by the LB-set's DNS name. If you don't want to use AWS or AWS-specific deployment tools, you could use Puppet Pipelines to do the same on Google Cloud or Azure. Puppet Pipelines was built by people who previously built some of those internal Amazon tools and offers similar functionality but cross-cloud. And if you want even fewer moving parts, just go PaaS or serverless.
Off topic: does google.com run on GCP? I ask because since 2010, Amazon.com has been running on AWS. ▶ this video (Around 7m30s into video)
Geez, oh yes. They built their platform and decided to start reselling it. That's why Netflix, Pintrest, Airbnb, Expedia, Foursquare, NASA, the MLB all use AWS. They converted 100% in 2011 according to Jon Jenkins ▶ this video
Every developer does have the ability to deploy to production and roughly 0.001% of deployments cause an outage, but this is a company where the mean time between deployments on an average weekday is 11.6 seconds. Source: ▶ this video
Amazon runs all of the Amazon.com web servers on EC2 hosts (and has since 2010: ▶ this video ). They've just made sure that they have enough hosts in each of the other AZs to withstand an outage.