Post

A warm request to a Netlify Edge Function now spends about 6ms on our side before the response heads back out. It passes through an edge node, a compute node, and a Firecracker MicroVM without leaving our network.

The request lands on the Netlify edge node closest to the client. The node terminates TLS and checks the path against the deploy's Edge Functions routes. Anything without a matching route goes on to the cache and origin as usual.

When a route matches, the edge node writes a spec for the machine that will run the function. It names the runtime, our platform image, and the function image. It also sets CPU, memory, and connection limits.

The edge node picks a compute node with rendezvous hashing, so a function lands on the same node every time. Its MicroVM stays warm and its code stays cached. When one site takes a big share of a region's traffic, we spread it across a slice of nodes.