<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Serverless on Antonio Cortés (DrZippie)</title><link>https://antoniocortes.com/en/tags/serverless/</link><description>Recent content in Serverless on Antonio Cortés (DrZippie)</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 13 Oct 2026 15:29:58 +0200</lastBuildDate><atom:link href="https://antoniocortes.com/en/tags/serverless/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Lambda now runs plain HTTP servers: meet Web Functions</title><link>https://antoniocortes.com/en/lambda-web-functions/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate><guid>https://antoniocortes.com/en/lambda-web-functions/</guid><description>&lt;p&gt;Two weeks ago I wrote about &lt;a href="https://antoniocortes.com/en/netlify-edge-firecracker/"&gt;how Netlify swapped V8 isolates for Firecracker microVMs&lt;/a&gt; in its Edge Functions, and I closed by saying microVMs were becoming the default for running third-party code, with Lambda as an example. Today AWS published &lt;a href="https://aws.amazon.com/blogs/aws/announcing-aws-lambda-web-functions-for-fast-consistent-web-app-performance-anywhere/"&gt;Announcing AWS Lambda Web Functions&lt;/a&gt;, and it&amp;rsquo;s a change to the programming model more than to the infrastructure: Lambda can now run &lt;strong&gt;a plain HTTP server&lt;/strong&gt;, the kind that listens on a port, without rewriting it as an event handler.&lt;/p&gt;</description></item></channel></rss>