Serverless architectural patterns
summary
Shows concrete serverless choices and tradeoffs: use API Gateway 29s timeout to justify background work; use SQS/SNS/Kinesis/DynamoDB Streams for brokering with differing retry, retention and cost profiles (Kinesis: per-shard concurrency, up to two-week retention; DynamoDB Streams: free with table); SQS lacked native Lambda trigger in 2018. Recommends decoupled invocation, pub‑sub, cron via CloudWatch Events, and sagas implemented with Step Functions and compensating actions. Notes default limits like default 1000 concurrency limit and that Kinesis shard controls concurrency, gives multi‑region, Athena/Macie examples and production lessons.
AI-written summary · about
chapters (15)
- 0:00Introduction to serverless
- 1:36Defining serverless
- 3:46Benefits of serverless
- 6:37Architectural patterns
- 8:26Real-world context
- 9:54Automation patterns
- 13:10User authentication
- 15:47Data processing pipelines
- 18:34Event-driven microservices
- 21:59Workflow orchestration
- 23:26Decoupled invocations
- 27:13Managing concurrency
- 30:37Event broker selection
- 40:57Saga pattern
- 44:27Monitoring and lock-in
related talks
48mServerless design patterns
49mServerless Architectural Patterns and Best Practices
40mCloud architecture patterns, how to implement them in a serverless way
39mBuilding Resilient Serverless Applications
50mServerless Architecture Patterns and Best Practices
53mBottlenecks in Serverless Applications
47mServerless Kafka Patterns.
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
