Best practices for serverless developers
summary
Argues that most Lambda glue code should be replaced with configuration and managed services to cut cost and maintenance, demonstrating direct integrations: Step Functions SDK integrations, API Gateway velocity templates, and EventBridge Pipes replace common functions. Shows tools for tuning: Lambda Power Tuning and Compute Optimizer to pick memory/Graviton2 vs x86, notes memory scales CPU and billing math so higher memory can lower cost, reports less than 1% cold starts in production, and recommends Power Tools plus X‑Ray, structured logs, and Lambda function URLs.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:09Serverless mental model
- 6:30Serviceful serverless
- 18:05Lambda function optimization
- 28:06Cold start considerations
- 37:31Developer tooling
- 41:28Resources and next steps
related talks
43mBest Practices for Serverless Developers
30mEvolving Serverless Architectures
46mServerless Architecture Patterns and Best Practices
49mMeasuring and increasing developer productivity with the help of Serverless
42mAWS Lambda from the trenches
01h 00mServerless - reality or BS - notes from the trenches
23mSimplifying design complexities using Serverless Architecture on AWS
36mTransforming SaaS with Serverless Architectures