Why we chose our own compute over AWS Lambda Web Functions | Blog
Not investment advice. Muhabbit scores how much a story may matter, not which way to trade.
Easel has opted to run web applications on its own compute rather than adopt AWS Lambda Web Functions, after testing showed execution environments remained alive and billed for memory 313 to 411 seconds after their last request. The company found memory accounted for roughly 88% of calculated compute and request costs at list prices, despite its application using only 160–210 MB, with no configurable idle timeout to shorten environment lifetimes. Although the experiment cost only about two cents at list prices, Easel said the economics matter at its scale of supporting thousands of applications with unpredictable traffic, some receiving just a few requests per day. Attempts to terminate idle environments after 10 seconds cut metered time roughly 20-fold, but AWS logged each intentional exit as a runtime failure. Easel is now moving application execution onto self-operated servers while keeping traditional Lambda for overflow, giving it control over scheduling and shared capacity. The decision highlights how idle billing and timeout limits can outweigh the concurrency and active-CPU benefits that drew Easel to Web Functions in the first place.
Muhabbit's AI wrote this summary in its own words from Hacker News's report. It can get details wrong, so check the source.
Named in this story
AWS, Lambda Web Functions, Easel