The internal document, annotated by Amazon's CTO, details the origins of AWS Lambda, beginning with the challenges faced by customers managing EC2 fleets that often sat idle while awaiting tasks like writing to a database or processing files.
Lambda, driven by the needs of our customers, has evolved quite a bit in the last decade. When you read this PR/FAQ, you'll notice some things that have changed, and a handful of ideas that eventually turned into full-blown features.
Vogels reminds readers that Amazon has a long-standing tradition of crafting internal "press releases" to articulate what will be delivered to customers clearly. These documents require authors to be precise and thorough, supporting their ideas with data and ensuring clarity to avoid any confusion.
At some I recall throwing my arms skyward and indicating that it would be cool to simply toss the code into the air and have the cloud grab, store, and run it.
Collection
[
|
...
]