Velocity 2011: Jon Jenkins, "Velocity Culture"
O'Reilly1 HN recommenders · 2012–2018
52K views · talk · dated · Uploaded 2011-06-20
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.
1:24:13Micro Men - 720p (2009)
gimpymoo
56:09Project Code Rush - The Beginnings of Netscape / Mozilla Documentary
The Documentary Network
19:10Velocity NY 2013: Richard Cook, "Resilience In Complex Adaptive Systems"
O'Reilly
52:35Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017
GOTO Conferences
54:11Ed Catmull, Pixar: Keep Your Crises Small
Stanford Graduate School of Business
59:56AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401)
Amazon Web Services
1:04:04LISA11 - Fork Yeah! The Rise and Development of illumos
USENIX
28:36Literate Devops with Emacs
Howard Abrams
5 comments from Hacker News
Amazon runs all of the Amazon.com web servers on EC2 hosts (and has since 2010: [VIDEO] ). They've just made sure that they have enough hosts in each of the other AZs to withstand an outage.
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: [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 [VIDEO]
Off topic: does google.com run on GCP? I ask because since 2010, Amazon.com has been running on AWS. [VIDEO] (Around 7m30s into video)
Amazon describes its internal service architecture here: [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.