Velocity 2011: Jon Jenkins, "Velocity Culture"

Channel:O'Reilly · Length:15:14 · Published:2011-06-20 · Views:51868

Watch on YouTube

Summary

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.

Why HN recommends it

HN commenters cite it as a primary source for facts such as Amazon.com running on AWS and its very frequent deployments.

the mean time between deployments on an average weekday is 11.6 seconds. — HN, 2013

Cloud, DevOps & reliability · Tech company stories & documentaries

Subtitles (excerpt)

it's awesome to be here thanks for coming out this morning I know uh there was some partying last night so uh it's always a tough tough day to make it out on the second day um I'm always curious uh and uh velocity caters to two big populations web performance people and then operations people how many of you would consider yourselves primarily operations focused here okay pretty good and how many of you would consider yourselves primarily web performance focused interesting cool pretty good split well I've been asked here to talk to you a little bit today about velocity culture and specifically I'm going to focus on a little bit more of the Ops side and what I think is an unmet challenge in web Ops uh my argument today is going to proceed in kind of three parts first uh I think that the success of the Velocity culture overall depends on tying it to the business and real business metrics that matter secondly I'm going to argue that web performance has really succeeded in doing this incredibly well over the last several years in that there's actually an met challenge in Ops uh to to sort of meet the business focus uh and connect the dots for people uh as most of you know velocity started in 2007 at a meeting at

On Hacker News

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… — aphexairlines, 2018-06
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) — alberth, 2017-03
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] — mrjatx, 2014-12
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] — dxm, 2013-08
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. — yap, 2012-10

Related videos