<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>firecracker on Oleksandr Kulbida</title>
    <link>https://okulbida.com/tags/firecracker/</link>
    <description>Recent content in firecracker on Oleksandr Kulbida</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Tue, 23 Jun 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://okulbida.com/tags/firecracker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWS Lambda MicroVMs: stateful sandboxes with full lifecycle control</title>
      <link>https://okulbida.com/posts/aws-lambda-microvms-stateful-sandboxes/</link>
      <pubDate>Tue, 23 Jun 2026 00:00:00 +0200</pubDate>
      
      <guid>https://okulbida.com/posts/aws-lambda-microvms-stateful-sandboxes/</guid>
      <description>AWS just shipped something that reframes what &amp;ldquo;serverless&amp;rdquo; can mean. Lambda MicroVMs are not Lambda Functions with a bigger timeout. They are a fundamentally different primitive: stateful, VM-level isolated environments with an explicit lifecycle you control.
The key shift: instead of getting a recycled process for 15 minutes, you get a dedicated Firecracker microVM that lives up to 8 hours — and you decide when it starts, suspends, resumes, and terminates.</description>
    </item>
    
  </channel>
</rss>
