Deep dive into Durable Functions
summary
Shows a concrete durable functions setup: an HTTP starter launches an orchestrator that goes to sleep and restarts between activity functions, enabling fan-out/fan-in parallelism so 300 page updates can run concurrently instead of 33 minutes serially. Notes platform limits like 5 minute timeout on activity runs in consumption mode, cold starts of a few seconds, mandatory Azure Storage for state, and gotchas such as serialization traps (internal properties, self‑referencing loops) and how to purge or version orchestration state.
AI-written summary · about
chapters (24)
- 0:00Start
- 3:20Free Tier
- 4:28Azure Serverless Services
- 5:08Kubernetes
- 6:47Consumption Mode
- 7:42The Timeout in Consumption Mode
- 8:55Why Durable Functions Were Created
- 14:20Function Chaining
- 16:31Demo
- 17:13How To Create a Function a Durable Function Application
- 17:55Durable Function Orchestration
- 20:50Activity Trigger
- 21:45Rest Client
- 27:52Terminate a Function Application
- 28:18Fan Out Fan in
- 31:45Tips and Tricks
- 33:15Tricks for Debugging
- 33:38Non-Deterministic versus Deterministic
- 43:36Serialization
- 47:41Error Message
- 49:05Awaiting Orchestrator
- 50:56Multi-Threaded Execution
- 51:51Debugging
- 55:50Anatomy of a Durable Function Application
related talks
58mDeep dive in Durable Functions
58mAdvanced Serverless Workflows with Durable Functions
48mDelightful Durable Function Patterns
42mAzure Durable Functions for Serverless .NET Orchestration
56mAzure Durable Functions for serverless .NET orchestration
53mDeep dive into Azure Durable Functions
41mAzure Durable Functions for Developers
59mFunction Orchestration in the World Of Serverless