Best Practices for Serverless Developers
summary
Claims concrete tuning steps and surprising numbers: EventBridge latency drops 94% so async becomes near-synchronous; cold starts impact <1% of production invokes; use Step Functions with 200+ service integrations and 14,000 API actions to replace glue code; prefer configuration (EventBridge Pipes, AppSync, direct SDK integrations, SnapStart, provisioned concurrency) over custom Lambda runners; measure and tune memory/Graviton with Lambda Power Tuning; use PowerTools for observability, batching, idempotency and DLQ/redrive handling.
AI-written summary · about
chapters (16)
- 0:00Serverless best practices
- 1:06What serverless means
- 6:01Serviceful serverless
- 8:08Orchestration vs choreography
- 10:16Optimizing workflows with Step Functions
- 12:48Step Functions standard vs express
- 14:35When to use Lambda
- 17:03Understanding Lambda cold starts
- 20:52Lambda pricing and tuning
- 24:03Lambda scaling and quotas
- 26:51Production-ready serverless
- 32:07Observability for serverless
- 35:32Serverless security
- 36:35Scaling best practices
- 37:58Lambda development tools
- 39:43Closing and resources
related talks
42mBest practices for serverless developers
30mEvolving Serverless Architectures
36mTransforming SaaS with Serverless Architectures
23mSimplifying design complexities using Serverless Architecture on AWS
49mMeasuring and increasing developer productivity with the help of Serverless
31mAccelerate business innovation with serverless applications
19m(N+1) Lessons I learned about serverless
46mServerless Architecture Patterns and Best Practices