Serverless Architecture Patterns
summary
Draws patterns from real projects: functions (Lambda/Cloud Functions) for bursty workloads, containers and Kubernetes when startup latency or custom runtimes matter, and hybrid steps like using micro VMs first. Gives concrete numbers and outcomes — a census prototype costs $500 in service costs and a training platform scales to 800,000 customers, an enterprise IoT shipped in 10 months — and describes tools used: S3/Cloud Storage, DynamoDB/RDS, EMR/Dataproc with lift-and-shift to EMR then Kubernetes for 500‑hour jobs cut to ~10 minutes.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 4:13Why serverless
- 6:46Serverless story
- 9:14Amazon Lambda
- 10:16Functions
- 13:57Compute
- 16:56Kubernetes
- 17:51Peer Functions
- 20:22Logging
- 22:21Lambda Council
- 23:46Log Reader
- 24:29Serverless
- 32:05Typical Architecture
- 35:33What do we learn
- 38:10Benefits
- 39:05Key takeaways
- 39:44Lynns story
- 40:35Data
- 41:25Genomics
- 41:47Australia
- 43:11Amazon
- 44:07Lambda
- 49:23Pipelines
- 52:20Cursed Forest
- 55:13Elastic MapReduce
- 56:13Data Lake
- 58:39BigQuery
related talks
49mServerless Architectural Patterns and Best Practices
55mServerless Design Patterns for the Enterprise with AWS Lambda
47mAdvanced Serverless Architectural Patterns on AWS
50mServerless Architecture Patterns and Best Practices
46mServerless Architecture Patterns and Best Practices
01h 00mServerless - reality or BS - notes from the trenches
58mServerless: Five Key Things you need to Know
45mPatterns & practices for developing enterprise-scale serverless applications