Durable Functions #10: How to Write Safe Orchestrations

GitHub repo with the demo project:

Azure Functions Docs about Orchestrator Code Constraints:

Durable Functions Code Snippets:

One of my more in depth sessions about Durable Functions:

[williamnoel]

So great. Thanks, never knew that the analyzer existed. Can’t wait to fire it up.

[georgemoldovan]

Hi Marc, great content, it was much needed! Do you know if this analyzer can be used for a project that uses directly the Durable Task Framework without relying on Durable Functions? I'm using DTFx with a SQL Provider for running some durable workflows using my own infrastructure, and it would be great if I could take advantage of these analyzers. But for now, it doesn't seem to work for non-serverless solutions, but maybe there is a workaround that I'm not aware of ...

[brunowillian]

Hi Marc, hope you are doing great during these challanging times. Great video!

So I've running some tests myself I got a bit confused around Durable Entities behaviour and would love to hear from you.







When I first read that, along with the concept of durable entities I was like, does that mean I can create a counter that won't ever bring me duplicate number regardless how many simultaneous requests I make?



So I created a Counter and called it from another application (power automate), I make hundreds calls and my counter gives me a lot of duplicated numbers, is that behaviour expected? Is there a way to prevent those duplicated numbers?


Thanks in advance