Serverless but Stateful! - Azure Durable Functions Are AWESOME!
Vložit
- čas přidán 30. 06. 2022
- Running a standard Azure function is usually not well suited to long running tasks that require management of state. That's where Durable Functions come in!
In this demonstration, I demonstrate how you can create an Azure function that starts a long running piece of logic, but also can wait for external events, be cancelled etc thanks to the built in orchestration tools that allow you to manage state.
If you haven't already, check out this video for an introduction to Azure Functions. • Let's go SERVERLESS - ...
#dotnet #.NET #azure #MicrosoftAzure #csharp #azurefunctions #softwaredevelopment #programming #durablefunctions - Věda a technologie
You deserve a coffee , well done bro
Sweet. This was really helpful. Explained well too. Not a lot of fluff along the way. Just strait to the point. 🤘
Glad it helped!
GoAhead is a command, not an event. Event is a fact, it can't be imperative. Great overview, thank you!
Very helpful, thank you
Glad to hear it!
Currently working on an AWS project and I wish we had something like this.
Does AWS lambda not have an equivalent? I couldn't find one.
@@nickproudprogrammer Dealing with GUI garbage called Amazon Step Functions. Development is so slow and difficult to test.
It's basically drag and drop browser UI tool that generates a JSON code. Then we copy the JSON code to our Terraform project.
I would say it's the worse thing I ever worked with since we're just wasting time. I can do all of the orchestration logic much faster with Java + Spring Boot.
More money for Bezos I guess.
So this is basically synchronization via message passing in the cloud.. interesting.. I am not sure how reliable though. What happens with concurrent commands that contradict each other (GoAhead=true/false) or duplicate commands (GoAhead 2 or more times because of retries)?
Question: would it be sensible to have a TimerTrigger function to do a thing you need it to do, this TimerTrigger then shoots off a start to the durable function and then each time the timer starts again you check on the status of the durable function, if it's not completed, exit, if it's completed, trigger it again? Or is that stupid?
Nothing is stupid 😁. Sounds like you want to automate the process of checking in on a long running function. What you've outlined makes a lot of sense based on the limited context I have about your project