Durable!
• Stateful functions
• Managed state, checkpoints, and restarts when needed.
• Define stateful workflows in orchestrator functions.
.
Slide 3
Slide 3 text
Workflows you said?
• Define workflows in code. No JSON schemas or designers are
needed.
• 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.
Slide 4
Slide 4 text
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.
Slide 5
Slide 5 text
Function chaining
DEMO
Slide 6
Slide 6 text
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
Slide 7
Slide 7 text
Fan-Out
DEMO
Slide 8
Slide 8 text
Problem 3 : Eternal Processes
• Long running processes
• Built-in state management
• orchestrationClient or built-in webhooks can be used.
Slide 9
Slide 9 text
Problem 4 : Stateful Singletons
• Actor like scenarios.
• Long-running (possibly endless), stateful, reliable, single-
threaded, location-transparent, and globally addressable.
Slide 10
Slide 10 text
Stateful Singletons
DEMO
Slide 11
Slide 11 text
Problem 5 : Human Interaction
• Durable timers to wait for external events.
• orchestrationClient binding can be used to use built-in
bindings.