Serverless Design Patterns for the Enterprise with AWS Lambda
summary
Argues that deploying per-request functions is the right cloud abstraction and shows a working squirrelbin demo built with AWS Lambda, API Gateway, S3 and DynamoDB where a single function returns "pong" and the site runs with no servers. Describes event patterns (S3 thumbnails, Kinesis shards for parallel streams), runtime details (Linux containers + warm pools), scaling to 50,000 TPS and a secure eval sandbox for running user code. Pricing: 20¢ per million requests with a 1M-request free tier.
AI-written summary · about
chapters (22)
- 0:00Start
- 4:27[Micro] Application Design for the Cloud
- 5:18The Serverless Compute Manifesto
- 7:41AWS Lambda and Amazon API Gateway
- 12:13How to Run a 1 Hour Task
- 13:50What Programming Model???
- 20:46Events: JSON + Functions
- 22:07Example: Build an audit system in 5 minutes
- 23:00Frameworks Bad; Services Good
- 24:04Drill-down: Resource Sizing in AWS Lambda
- 25:26Drill-down: Versioning
- 28:19But what *is* it?
- 31:59Serverless Web Apps
- 33:42Principle of Complexity Concentration
- 35:04Amazon S3 Bucket Triggers
- 35:59Aside: Functions for Behavioral Abstraction
- 37:02Real-time Analytics Processing
- 38:17How Work Arrives
- 40:05New App Ecosystems: Alexa Apps + Slack = Serverless Bots!
- 41:25New App Ecosystems: Integration
- 42:29Customer Success Stories
- 43:35Pay-per Request
related talks
49mServerless Architectural Patterns and Best Practices
01h 02mServerless Architecture Patterns
54mServerless Architectures: no servers allowed!
47mAdvanced Serverless Architectural Patterns on AWS
50mServerless Architecture Patterns and Best Practices
20mWhy Serverless Architecture is Changing Software Development
46mServerless Architecture Patterns and Best Practices
54mContainerless in the cloud with AWS Lambda