Velocity 2011: Jon Jenkins, "Velocity Culture"

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.