Serverless Best Practices
summary
Shows concrete patterns and tools: use the VS Code Functions extension for local dev, wire an HTTP trigger to a blob output plus a queue message and process that blob in a separate queue-triggered function, and prefer SDK calls when you need more than read/write (example: Cosmos DB deletes). Emphasizes that functions share a function app runtime so reuse clients and avoid per-execution connections, compares consumption vs premium/dedicated for cold-start and cost tradeoffs, and points to the Diagnose and Solve pane and GitHub repo for troubleshooting.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:00Session Structure
- 3:25Functions vs Code Extension
- 5:40Bindings vs SDK
- 7:20Function Apps
- 10:00Scaling
- 13:00Troubleshooting
related talks
40mFrom Your Workstation to Production: The Serverless Development Lifecycle
51mServerless – are you ready for the revolution?
01h 01mDos and Don'ts for Serverless and Azure Functions
01h 00mServerless Trends of the Season
27mServerless Applications - Azure Functions, API Mgmt., Insights
39mServerless at the end of the Universe
43mServerless Application Development using
48mServerless beyond functions