Every Node process you deploy runs on an operating system built for thousands of programs it will never run. Drivers for hardware you don't have. A scheduler managing processes that don't exist. You pay for all of it in image size, boot time, and attack surface. Unikernels compile the application together with only the OS parts it actually uses, producing a single specialized VM image. One app, one kernel, nothing underneath. I'll take an ordinary Express server and boot it as its own operating system, live. Then I'll spend the second half on what breaks. Some of it fails outright. Some of it works in ways that will surprise you once you know there's no separate userspace. By the end you'll know what a JavaScript runtime actually requires from a machine, and how much of the stack below your code is optional.
Utibeabasi Umanah is an SRE at Unikraft. Before that he built and operated distributed systems at scale, from multi-region IPFS gateways at Fleek to production Kubernetes platforms at Matrica and infrastructure at HeartStamp. He spends most of his time thinking about isolation, sandboxing, and making infrastructure disappear behind good abstractions.
