Fluid compute: How we built serverless servers

What this post added

This post details the foundational work of building a custom TCP-based transport layer to enable streaming responses from AWS Lambda, which evolved into the ability to multiplex multiple concurrent requests to the same Lambda instance, breaking the traditional one-invocation-per-instance model. A new service, `compute-resolver`, was built to coordinate routing requests to Vercel Function Router pods, increasing the chances of reusing existing TCP connections and preventing hot-spotting.