4 ms·
Amazon describes its internal service architecture here: https://www.youtube.com/watch?v=dxk8b9rSKOo https://www.youtube.com/watch?v=dxk8b9rSKOo Services use
by aphexairlines 8y ago
Amazon describes its internal service architecture here:
https://www.youtube.com/watch?v=dxk8b9rSKOo https://www.youtube.com/watch?v=dxk8b9rSKOo
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.
- auslander 8y agoNever heard of Apollo, had to dig :) In short, it is a predecessor of AWS CodeDeploy. www.allthingsdistributed.com/2014/11/apollo-amazon-deployment-engine.html