For more than ten years, AWS Lambda has meant one thing to most of us: write a handler, attach a trigger, and let AWS take care of everything else. In July 2026, AWS launched Lambda MicroVMs, and “Lambda” now covers a second, quite different kind of compute.
So if you’re designing a new workload today, you’ll probably ask yourself: should this be a Lambda function or a MicroVM? In this post I’ll cover how each one works, where they differ, and a simple way to choose between them.
The Shared Foundation: Firecracker
The two services have more in common than you might expect. Every Lambda function invocation already runs inside a Firecracker microVM. That’s the lightweight virtualization technology AWS open-sourced, and it gives you hardware-level isolation with very fast startup. Lambda SnapStart then used Firecracker’s snapshotting to restore pre-initialized environments instead of booting …

