HackerTubewatch
Surprise me
Frame from AWS re:Invent 2018: [REPEAT 1] A Serverless Journey: AWS Lambda Under the Hood (SRV409-R1) Plays via YouTube's privacy-enhanced embed

AWS re:Invent 2018: [REPEAT 1] A Serverless Journey: AWS Lambda Under the Hood (SRV409-R1)

11 videos recommended on HN
YouTube
2 HN users recommended this talk2 months2019 score 2
Years with an HN recommendation, 2007–2026

HN cites it as the authoritative description of Lambda internals and isolation, by the engineers who built it.

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.

“You can watch this talk to learn more” (HN, 2019)

2 recommendations · 1 citations · Talks · advanced · partly dated

3 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@staticassertion Jan 2019 Recommends
on HN thread 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.
Explains Lambda sandboxing internals and isolation.
@appwiz Jun 2019 Recommends
on HN thread 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]
Talk on Lambda internals from reInvent 2018.

Citations, criticism and jokes

@discodave Mar 2019 Cites it
on HN thread On Internal Engineering Practices at Amazon
Read more
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. * EC2 launched in 2006 (7 years before Docker). * Apollo (and the build system Brazil) predated EC2 by many years. * Amazon.com was migrating to EC2/AWS before 2012 ( [link] ) * Another example, Lambda, which launched in 2014 runs on EC2 ( [this video] ). * New services get to build in AWS and use Lambda, ECS, DynamoDB etc based on their business needs.
Cited to show Lambda runs on EC2.

Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.

Keyboard shortcuts

/
Search
j k
Next / previous video
r
Surprise me
l
Like (video page)
w
Watch later (video page)
?
This help
Esc
Close