Skip to content
Hallway
0:00 / 0:00

#amazon#apollo#velocityculture

Velocity 2011: Jon Jenkins, "Velocity Culture"

O'Reilly

202K subscribers • 23 videos on Hallway

YouTube
  • Recommended by 1 person: 1 on Hacker News.
  • Presented by Jon Jenkins, Director of Platform Analysis at Amazon.com
  • May be out of date. Uploaded 15 years ago, in an area where tools change fast.

Intermediate. Assumes working knowledge.

51K views15 years ago1 recommendation

Cloud and DevOpsCareers and interviewsAWSCI/CD and deploymentInside tech companies

Jon Jenkins explains how Amazon's operations culture, deployment frequency, and internal tools like Apollo drove their migration to AWS.

Operations is can play a critical role in driving revenue for the business. This talk will explore some ways in which the ops team at Amazon is thinking outside the box to drive profitability. JJ will also issue a challenge for next year's Velocity Conference Jon Jenkins Amazon.com Jon Jenkins is the Director of Platform Analysis at Amazon.com. He leads a team focused on designing and implementing highly-available architectures capable of operating within tight performance requirements at massive scale with minimal human intervention. Jon still loves getting his hands dirty and can't resist the thrill of solving emergent problems. Prior to joining Amazon Jon spent time at several startups and he has a strong background in personalization technologies.

Why it's here

1 person recommends this

What people say. Highly recommended for its insights into Amazon's early deployment frequency, internal service architecture, and transition to AWS.

aphexairlineson Hacker News • Recommends

On “Four years after its release, Kubernetes has come a long way”

Amazon describes its internal service architecture here: link to 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.
View on Hacker News

yapon Hacker News • Mentions

On “Amazon EC2 currently down. Affecting Heroku, Reddit, Others”

Amazon runs all of the Amazon.com web servers on EC2 hosts (and has since 2010: link to this video ). They've just made sure that they have enough hosts in each of the other AZs to withstand an outage.
View on Hacker News

dxmon Hacker News • Mentions

On “Amazon was down”

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: link to this video
View on Hacker News

mrjatxon Hacker News • Mentions

On “AWS CodeCommit”

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 link to this video
View on Hacker News

alberthon Hacker News • Mentions

On “Always Free Usage Limits”

Off topic: does google.com run on GCP? I ask because since 2010, Amazon.com has been running on AWS. link to this video (Around 7m30s into video)
View on Hacker News