zlacker

>>hugodu+(OP)
"the fork was very very bad for eating soup - this is a story about how we migrated to a spoon"

...firecracker does fine what it was designed to - short running fast start workloads.

(oh, and the article starts by slightly misusing a bunch of technical terms, firecracker's not technically a hypervisor per se)

>>lessal+5f
..so is it more to support directly deploying functions to the cloud? Like, what AWS Lambda and CloudFront Functions might be built on?

>>sheeps+vg
yes, it was created originally for AWS Lambda

mainly it's optimized to run code only shortly (init time max 10s, max usage is 15min, and default max request time 130s AFIK)

also it's focused on thin server less functions, like e.g. deserialize some request, run some thin simple business logic and then delegate to other lambdas based on it. This kind of functions often have similar memory usage per-call and if a call is an outlier it can just discard the VM instance soon after (i.e. at most after starting up a new instance, i.e. at most 10s later)