MicroVMs: Run isolated sandboxes with full lifecycle control (aws.amazon.com)

Article summary

AWS Lambda introduces MicroVMs, a new serverless compute primitive that allows running code in isolated, stateful execution environments with virtual machine level isolation and near-instant launch and resume. MicroVMs are powered by Firecracker, a lightweight virtualization technology, and are designed for multi-tenant applications that need to execute user- or AI-generated code. Each MicroVM gives a single end user or session its own isolated environment that launches rapidly and retains memory and disk state for the length of the session. MicroVMs support up to 8 hours of total runtime and can be suspended automatically after a configurable idle window.

Main themes

• Serverless Compute
• Virtual Machine Isolation
• Stateful Execution
• Multi-tenant Applications
• Cloud Computing
• Firecracker Technology

What commenters say

• The introduction of MicroVMs is a significant development for applications that require isolated and stateful execution environments.
• Some commenters are concerned about the lack of GPU support in MicroVMs, which may limit their usefulness for certain workloads.
• MicroVMs are seen as a more cost-effective and scalable solution compared to some existing sandbox providers, but others argue that they are still overpriced and may not offer the same level of service as hyperscalers.
• The 8-hour runtime limit for MicroVMs may be a limitation for some use cases, such as long-lived developer environments, but others argue that this can be mitigated by using external storage solutions like EFS.
• Some commenters prefer self-hosted solutions over cloud-based services like AWS, citing concerns about cost, security, and reliability.
• The pricing model for MicroVMs is seen as a major factor in its adoption, with some arguing that it is still too expensive and others finding it cost-effective for certain workloads.
• The comparison between MicroVMs and other cloud services, such as Google Cloud Run, highlights the trade-offs between different solutions and the importance of choosing the right tool for the job.
• The use of Firecracker technology in MicroVMs is seen as a key factor in its performance and security, but some commenters are concerned about the potential for memory bloat and other issues.