4 ms·
EC2 instance boots in 2 to 3 minutes, a Docker container starts in seconds. You can specify precisely how much CPU/Memory you need for a container, with a VM, y
by iampims 4y ago
EC2 instance boots in 2 to 3 minutes, a Docker container starts in seconds.
You can specify precisely how much CPU/Memory you need for a container, with a VM, you're stuck with what the cloud provider offers.
You still need to get your app artifacts on that VM, how do you plan to do this?
EC2 (VM abstraction) is great for some type of software, but don't forget you'll also need a Load Balancer, provisioning TLS certs, security groups, autoscaling groups, VPN, public/private subnets…
- hintymad 4y agoOh, I love container-based deployment. I was just wondering if it’s worth building abstractions like EC2 that requires very little learning to use, use EC2-like systems to manage machines that host containers
- coredog64 4y agoThat’s ECS without the Fargate.
- nathants 4y agoec2 alpine on t3.small boots in 30 seconds. 45 seconds for spot. default-like vpc with public subnets and internet gateway is fine. zero trust. route53 health checks and returns up to 8 hosts in random order. to the gp’s point, using aws sdk to manage ec2 is shockingly easy. a lambda on a 1 minute timer with an aws sdk runs circles around autoscaling groups et al.
- dehrmann 4y ago> with a VM, you're stuck with what the cloud provider offers AWS has a very big menu of machine types.
- speedgoose 4y agoA lot of choice yes, but they are all either slow or overpriced.
- dx034 4y agoKubernetes on AWS won't be cheaper. And if you go with another provider, they're likely to also have an API to automatically provision VMs.