This is part of a full day Serverless training I hosted for Microsoft Turkey in Istanbul talking about Azure Durable Functions.
Azure Durable Functions
• Stateful functions
• Managed state, checkpoints, and restarts when needed.
• Define stateful workflows in orchestrator functions.
Workflows you said?
• Define workflows in code. No JSON schemas or designers are
• They can call other functions synchronously and asynchronously.
Output from called functions can be saved to local variables.
• They automatically checkpoint their progress whenever the
function awaits. Local state is never lost if the process recycles.
Problem 1 : Function Chaining
• No visualization to show relationship between functions and queues.
• Middle queues are an implementation detail – conceptual overhead.
• Error handling adds a lot more complexity.
Problem 2 : Fan-out/Fan-in
• Fanning-out is easy, but fanning-in is more complicated.
• Functions offers no help with this scenario today
• All the same problems of the previous pattern
Problem 3 : Eternal Processes
• Long running processes
• Built-in state management
• orchestrationClient or built-in webhooks can be used.
Problem 4 : Stateful Singletons
• Actor like scenarios.
• Long-running (possibly endless), stateful, reliable, single-
threaded, location-transparent, and globally addressable.
Problem 5 : Human Interaction
• Durable timers to wait for external events.
• orchestrationClient binding can be used to use built-in
Links worth sharing
Durable Task Framework
Durable Functions Nuget Package
http://daron.me | @daronyondem
Download slides here;