Where Did All My Servers Go?
summary
Demystifies serverless by showing AWS concrete tradeoffs: Lambda functions with a five‑minute timeout and payload limits, Route53 + API Gateway + Lambda + SQS wiring for a mailing workflow, and an OAuth-like front end that issues DynamoDB TTL tokens to secure legacy internal APIs; explains failures from S3 eventual consistency, increased latency from extra network hops, need for DLQs and retry logic, and that cost savings are large only when slicing logic correctly and applying serverless to appropriate workloads.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:07Garth Henson
- 1:45What Is Serverless Server this Computing
- 5:25Benefits of Service
- 6:23Scalability
- 6:48The Most Common Currency To Pay for Benefits in Our Application Architecture
- 7:35Microservice Infrastructure
- 9:31Eventual Consistency
- 11:55Fault Tolerance
- 14:38Lambdas
- 15:27S3
- 15:47Dynamodb
- 19:55Authorizer
- 21:52Api Gateway
related talks
51mConfusion In The Land Of The Serverless
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
39mBuilding Resilient Serverless Applications
29m2 Years, 0 Servers: Lessons learned from running a startup 100% on Serverless
01h 00mNo, I don't need servers for .NET development in AWS!
01h 00mServerless - reality or BS - notes from the trenches
42mServerless Tales from the Trenches
28mCostly mistakes in serverless computing