When AWS announced Lambda Web Functions in October, I was excited.

At Easel, we'd spent months building infrastructure to run web applications efficiently on traditional Lambda. Native HTTP servers, concurrent requests, and active CPU billing sounded like exactly what we'd been looking for.

If Web Functions worked the way we hoped, we could potentially replace a substantial amount of our custom infrastructure.

So we decided to put them to the test.

A few weeks later, we'd decided to run our own compute instead. And as it turns out, our own infrastructure was faster, too.

The five-minute problem

Our initial experiments were promising. Web Functions handled 300 concurrent requests without errors, and a new function was serving requests in under nine seconds.