Best practices for building interactive applications with Lambda
summary
Practical guidance for building interactive backends: use AWS Lambda with API Gateway or the new Lambda function URLs (HTTPS, SigV4 IAM or custom auth, CORS configurable) for simple webhooks; function URLs share Lambda limits: 15-minute timeout, 6 MB payload, and no extra per-call cost. Lambda now supports up to 10 GB ephemeral storage and memory; cold starts occur in less than 1% of invocations and are usually under 100 ms—reduce them by minimizing package size, using modular SDK v3 and initializing resources outside the handler.
AI-written summary · about
chapters (10)
- 0:00Introduction and goals
- 1:27Serverless in production
- 3:24Scaling and core concepts
- 8:41Synchronous vs. asynchronous
- 14:20Building interactive apps
- 19:40Lambda function URLs
- 24:54Configuring function URLs
- 30:49Use cases and optimization
- 36:58Optimizing cold starts
- 45:45Comparison and conclusion
related talks
33mAWS Lambda - Logic in the Cloud without Back-end
54mContainerless in the cloud with AWS Lambda
58mAWS Lambda and Serverless Framework Deep dive
39mThink in Cloud, Develop in Cloud
31mA quick intro to AWS Serverless
47mReal Use Cases for Using AWS Lambda for Infrastructure Tasks
42mServerless Tales from the Trenches
39mHow to Go with AWS Lambda?