Deep dive in Durable Functions
summary
Azure Durable Functions provide code-based workflow orchestration on Azure with fan-out/fan-in parallelism and long running steps by using a special orchestrator that serializes state to Azure Storage and then orchestrator sleeps to avoid billing. Practical limits include a consumption timeout of 5–10 minute timeout (premium ~30 minutes). Example: automation that rebuilds docs.microsoft.com session pages for ~300 sessions every 30 minutes runs ~30 minutes locally but ~2 minutes on Azure. Gotchas: avoid local files, keep serialization public (no internal setters), never await non‑context tasks, and manage task hub names when purging history.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:48Azure Functions Overview
- 4:56Durable Functions Purpose
- 6:52Real World Case Study
- 10:43Durable Functions Core Concepts
- 12:24Common Patterns
- 14:51Code Demonstration
- 20:01Parallel Processing Demo
- 25:42Advanced Patterns
- 27:23Tips and Tricks
- 34:21Debugging Gatchas
- 38:23Serialization and Workarounds
- 43:53Advanced Debugging and Closing
- 55:36Q&A
related talks
58mDeep dive into Durable Functions
42mAzure Durable Functions for Serverless .NET Orchestration
14mOvercoming Serverless challenges with Durable Functions
41mAzure Durable Functions for Developers
28mAzure Durable Functions - Stateful workflow on top of Stateless Architecture
58mAdvanced Serverless Workflows with Durable Functions
56mAzure Durable Functions for serverless .NET orchestration
48mDelightful Durable Function Patterns
