2 ms·
Lambda and most similar technologies use variants of containers, not VMs. Outside HN that distinction might not be important. Here being pedantically correct d
by nl 4y ago
Lambda and most similar technologies use variants of containers, not VMs.
Outside HN that distinction might not be important. Here being pedantically correct does matter on this because the VM abstraction has been around for a long time, whereas containers were an enabling technology for serverless.
And containers and the fast startup, security and resource consumption guarantees they offer is a big difference to the old days of shared PHP hosting.
And this is why "reinvention" with new technology is different.
- scarface74 4y agoLambda and Fargate use the Firecracker VM https://firecracker-microvm.github.io/ https://firecracker-microvm.github.io/ Firecracker is a virtual machine monitor (VMM) that uses the Linux Kernel-based Virtual Machine (KVM) to create and manage microVMs. Firecracker has a minimalist design. It excludes unnecessary devices and guest functionality to reduce the memory footprint and attack surface area of each microVM “How AWS’s Firecracker Virtual Machines work” https://m.youtube.com/watch?v=BIRv2FnHJAg https://m.youtube.com/watch?v=BIRv2FnHJAg The Lambda service team always emphasizes the level of isolation that Firecracker VMs gives you that containers don’t.
- yencabulator 4y agoAnd Google Cloud Run use gVisor, which is also not a container.