Get the latest tech news
AWS Lambda PR/FAQ After 10 Years
On AWS Lambda's 10th anniversary, I'm publishing the internal PR/FAQ that helped launch this groundbreaking service. This document provides insight into the customer problems we observed in the early 2010s and our vision for serverless computing. Readers will find annotations throughout, offering a glimpse into how our long-term thinking has influenced Lambda's evolution over the past decade.
When you read this PR/FAQ, you’ll notice some things that have changed (e.g., 1ms billing granularity and support for functions with 10 GB of memory), and a handful of ideas that eventually turned into full-blown features (which I’ve annotated in the text below). Large customers benefit from Lambda’s placement engine, which effectively compacts their workloads: Each new request is placed with respect to minimizing the number of instances dedicated to that account (subject to maintaining latency, throughput, and availability goals). Lambda can also lower TCO by maintaining the operating system, language runtime, and libraries on the customer’s behalf and, in collaboration with other AWS services, offering security, scaling, high availability, and job control for the applications it runs.
Or read this on Hacker News