AWS re:Invent 2018: [REPEAT 1] A Serverless Journey: AWS Lambda Under the Hood (SRV409-R1)
Why Hacker News recommends it
HN cites it as the authoritative description of Lambda internals and isolation, by the engineers who built it.
What it is
An AWS re:Invent 2018 session in which Holly Mesrobian and Marc Brooker explain how AWS Lambda is built, including its sandboxing, isolation and scaling architecture. It covers what happens under the hood when serverless code runs.
Recommended by 2 HN commenters across 2 different months, 2019 to 2019.
What Hacker News said
Recommends staticassertion · 2019-01 · on “Exploiting the Math.expm1 typing bug in V8”
I believe AWS does share customer information within a device, but with a lot of sandboxing below that. You can watch this talk to learn more: [this video] I think the threat model is basically that you'd need a KVM kernel 0-day + the ability to exploit it, so a point of privilege such as outside of the firecracker sandbox.
Recommends appwiz · 2019-06 · on “Learning to Build Distributed Systems”
Here are a couple videos from reInvent 2018: Jaso talking about DynamoDB internals [LINK] Marc talking about Lambda internals [this video]
Cites discodave · 2019-03 · on “On Internal Engineering Practices at Amazon”
AWS SDE here. The short answer is, in order to get your team to adopt something, you need to make the case that it's better for customers (including things like migration costs). If the modern thing is more efficient, is higher availability, increases velocity, and so on then the case can be made. Some specific examples based on things you cite: * For an example of something OSS or "modern" coming from AWS, checkout Firecracker (written in Rust): [LINK] * With regards to "reinventing wheels" Apollo + EC2 solves a lot (not all) of the problems that containers solve, and existed for years before containers became the hotness. * Docker, which brought containers to the masses launched in 2013. *