Serverless design patterns
summary
Practical patterns: move periodic work and ops scripts off always-on servers into cron jobs → Lambda via CloudWatch Events to save cost; auto-subscribe new CloudWatch log groups and set retention by reacting to CloudTrail createLogGroup events; use Cognito temporary credentials so clients write directly to Kinesis; prefer Kinesis for durable retries and controlled concurrency over SNS for spiky loads; avoid event chains for in-bound workflows—use Step Functions for stateful flows (API Gateway times out at 29s, Lambda max 5min, default regional concurrency 1,000).
AI-written summary · about
chapters (14)
- 0:00Introduction and background
- 3:52Serverless definition and evolution
- 8:42Design patterns overview
- 10:06Cron jobs and event-driven ops
- 15:01Web apps and authentication
- 17:52Multi-region architectures
- 18:34Data processing pipelines
- 21:43Event-driven microservices
- 25:12Orchestration vs choreography
- 28:04Invocation patterns and concurrency
- 36:08Pub-sub with SNS and Kinesis
- 40:40Database streams vs Kinesis
- 44:54Saga pattern for transactions
- 47:20Conclusion and Q&A
related talks
51mServerless architectural patterns
49mServerless Architectural Patterns and Best Practices
23mSimplifying design complexities using Serverless Architecture on AWS
55mServerless Design Patterns for the Enterprise with AWS Lambda
40mCloud architecture patterns, how to implement them in a serverless way
47mServerless Kafka Patterns.
46mServerless Architecture Patterns and Best Practices
01h 02mServerless Architecture Patterns
