logoalt Hacker News

ATechGuyyesterday at 11:36 PM3 repliesview on HN

These are all wrappers around VMs. You could DIY these easily by using EC2/serverless/GCP SDKs.


Replies

ATechGuytoday at 4:17 AM

To the commenters here: thanks for correcting me! So AWS is losing AI sandboxing market to GCP due to high cold start times of EC2...very interesting!

thundergolfertoday at 4:05 AM

Modal engineer here. This isn’t correct. You can DIY this but certainly not by wrapping EC2 which is using the Nitro hypervisor and is not optimized for startup time.

Nearly all players in this space use Gvisor or Firecracker.

eastontoday at 2:43 AM

You can and can’t, at least in AWS. For instance, you can’t launch a EC2 to a point you can ssh in less than 8-10 seconds (and it takes a while to get EBS to sync the entire disk from s3).

Many a time I have tried to figure a self scaling EC2 based CI system but could never get everything scaled and warm in less than 45 seconds, which is sucky when you’re waiting on a job to launch. These microvm as a service thingys do solve a problem.

(You could use lambda, but that’s limited in other ways).