Your Web News in One Place

Help Webnuz

Referal links:

Sign up for GreenGeeks web hosting
February 26, 2021 03:56 pm GMT

Azure Durable Functions - Developing Serverless Stateful Workflow

Knowledge Sharing Azure Durable Functions at my workplace

Yesterday, I had an opportunity to share technical knowledge with my colleagues at Forefront Consulting during our monthly meeting in our Technology division. I was glad to share insights and knowledge about the basics of one of my favorite Azure cloud services, Azure Durable Functions.

What are Azure Durable Functions?

Well, if you have not work with Azure development or familiar with Azure technologies, probably it is hard to understand right away what it is. I hope that this article will enlighten you and give you the basics of it. I personally like to share that this great serverless technology exists!

Azure Durable Functions is an extension of Azure Functions

Azure Functions is a serverless solution that allows you to write less code, maintain less infrastructure, and save on costs. Instead of worrying about deploying and maintaining servers, the cloud infrastructure provides all the up-to-date resources needed to keep your applications running. You focus on the pieces of code that matter most to you, and Azure Functions handles the rest.

Azure Durable Functions on the other hand is built on top of Azure Functions. It does more than an Azure Function can do, especially it being when you have to develop a serverless long-running stateful workflow from the code along with the Azure Function in a serverlessenvironment.

Major Benefits of Using Azure Durable Functions

  • If you want write complex approval workflows
  • If you need to write long-running tasks
  • If you need to work with multiple Azure Functions
  • If you need to the lifecycle of your tasks
  • If you need to create serverless stateful workflows that require human interaction, monitoring, and more

Azure Durable Task Framework - The Technology Behind!

Behind the scenes, the Durable Functions extension is built on top of the Durable Task Framework, an open-source library on GitHub that's used to build workflows in code. Like Azure Functions is the serverless evolution of Azure WebJobs, Durable Functions is the serverless evolution of the Durable Task Framework. Microsoft and other organizations use the Durable Task Framework extensively to automate mission-critical processes. It's a natural fit for the serverless Azure Functions environment.

Major Components in Azure Durable Functions

Client functions are the entry point for creating an instance of a Durable Functions orchestration. They can run in response to an event from many sources, such as a new HTTP request arriving, a message being posted to a message queue, an event arriving in an event stream. You can write them in any of the supported languages.

Orchestrator functions describe how actions are executed, and the order in which they are run. You write the orchestration logic in code and it is important that these functions are deterministic. Learn more about Deterministic APIs

Activity functions are the basic units of work in a durable function orchestration. An activity function contains the actual work performed by the tasks being orchestrated.
Entity functions define operations for reading and updating small pieces of state, known as durable entities.

Entity Functions are only available in Durable Functions 2.0 and above. They are currently supported in .NET and JavaScript.

Durable Functions have different patterns that are worth checking out. Read more about it Azure Durable Functions

Further Reading and Learning Resources

If you like this article, please reshare. Feel free to leave feedback and ask questions. Follow me Twitter or via my LinkedIn


Original Link: https://dev.to/jonahandersson/azure-durable-functions-developing-serverless-stateful-workflow-4787

Share this article:    Share on Facebook
View Full Article

Dev To

An online community for sharing and discovering great ideas, having debates, and making friends

More About this Source Visit Dev To