Serverless Tales from the Trenches
summary
One company runs an entirely serverless platform that logs 50 million Lambda invocations and ~27 million API Gateway requests in a month, transfers ~37 TB, and pays an AWS bill of about $1,500 with Lambda itself costing only ~$206. Architecture uses API Gateway, Lambda, DynamoDB global tables, CloudFront (largest cost), S3, SNS, Elastic Transcoder, Netlify, Travis CI and Cypress. Operational lessons include using Route 53 health checks for cross-region failover, dead‑letter queues for failed Lambda events, and function concurrency limits as a kill switch.
AI-written summary · about
chapters (36)
- 0:00Introduction
- 1:27Cloud Guru
- 2:58AWS Analytics
- 5:21Agility
- 6:03Architecture
- 8:22Frontend Failover
- 9:14Route 53 Health Check
- 9:58Route 53 Health Check Demo
- 11:48Delete Website Demo
- 12:31API Demo
- 12:46Disclaimer
- 14:48Demo
- 15:28Is it possible
- 15:47Transcoding Pipeline
- 17:11Dead Letter Cue
- 18:27Burning Down the House
- 18:50Concurrency Controls
- 19:23lambda function
- 20:10tips
- 21:59book
- 22:37patents
- 23:21API Proxy
- 24:29Fanout
- 25:00Stream Transform
- 25:20Transform Function
- 26:20Wrapup
- 27:16Questions
- 27:31Audience Questions
- 28:05Avoiding vendor locking
- 29:53Large connection pools
- 30:24What do you wish the lambda ecosystem had
- 33:50How to integrate with a legacy system
- 35:42DDoS attacks
- 37:11Containers are useful
- 38:56Learning new services
- 40:19Concurrency issues
related talks
54mServerless Architectures: no servers allowed!
42mAWS Lambda from the trenches
40mThe serverless startup
01h 04mMigrating to Serverless - an experience report
49mTales From the Serverless
47mServerless in production, an experience report
33mAWS Lambda - Logic in the Cloud without Back-end
01h 00mServerless Architecture - Tales from a world without servers