Why we chose our own compute over AWS Lambda Web Functions | Blog | Easel.sh

Easel evaluated AWS Lambda Web Functions to run web applications but discovered that execution environments continue billing memory for five to seven minutes after their last request. Because this idle memory cost made the service uneconomical for unpredictable traffic scales, the company built its own compute infrastructure instead. Benchmarks using the same Next.js application showed that Easel's self-operated host answered warm requests 1.5 to 3 times faster and achieved faster cold starts than AWS Lambda Web Functions. Open article →