Deep dive into Azure Durable Functions
summary
Deep dive into how Durable Functions actually runs: the runtime replays orchestrators from an event-sourced history table and stores current status in an instances table, uses a task hub with blob leases to implement a distributed lock across a configurable number of control queues, and sends activity work via a shared work item queue. Coverage includes the default Azure Storage provider layout (tables, blobs, leases), Netherite’s Event Hubs + page blobs + Faster backend, the SQL provider built on stored procedures, service-bus transactional behavior, and the in‑memory emulator for testing.
AI-written summary · about
chapters (8)
- 0:00Introduction to Durable Functions
- 7:26Workers and scaling in Durable Functions
- 13:00Storage provider internals
- 20:45Debugging Durable Functions internals
- 30:56Durable Entities explained
- 33:04Other durability providers overview
- 40:58Using Durable Task without Functions
- 50:59Q&A and resources
related talks
41mAzure Durable Functions for Developers
58mDeep dive in Durable Functions
56mAzure Durable Functions for serverless .NET orchestration
58mAdvanced Serverless Workflows with Durable Functions
48mDelightful Durable Function Patterns
42mAzure Durable Functions for Serverless .NET Orchestration
46mDeveloper Fundamentals of Serverless.NET Development with Azure Durable Functions
58mDeep dive into Durable Functions
