Post by account_disabled on Dec 5, 2023 4:22:00 GMT
This is an extension of Azure Functions that allows you to optimize processes in a serverless environment. Azure Durable Function consists of basic block types: Azure Orchestrator ClientFunction It is a kind of starter that starts a certain process. Most often it is triggered by an http request adding a record to the database uploading a file etc. OrchestratorFunction This is the process that controls our workflow. This is where we decide on the order of steps in our process.
Activity Function This is specific functionality e.g. downloading a record from the database sending an email issuing an invoice etc. Azure Durable Function how does it work in practice? Let's assume for the sake of example that we run a clothing store in which after receiving the Email Marketing List payment we want to present the customer with possible color versions and close the order after making the selection. The initial state would be as follows: Azure workflow purchasing process Let's try to answer the following questions: What stage of the process is the client currently at? How can we detect possible errors? If an error occurs can we redo a step or process? Can we parallelize individual.
How can we receive confirmation of the customer's selection? As you can see there are many problems. The process is not perfect and cannot be easily controlled. Let's do it right! We start with the starter: Azure Functions We have created a function that is triggered by an http request and receives information about the order. Its key element is an IDurableOrchestrationClient object that starts the selected process. It's time to use the orchestrator. In its initial simplified form it may simply look like this: Azure functions starter As you can see this is the place from which we can control the entire ordering process.
Activity Function This is specific functionality e.g. downloading a record from the database sending an email issuing an invoice etc. Azure Durable Function how does it work in practice? Let's assume for the sake of example that we run a clothing store in which after receiving the Email Marketing List payment we want to present the customer with possible color versions and close the order after making the selection. The initial state would be as follows: Azure workflow purchasing process Let's try to answer the following questions: What stage of the process is the client currently at? How can we detect possible errors? If an error occurs can we redo a step or process? Can we parallelize individual.
How can we receive confirmation of the customer's selection? As you can see there are many problems. The process is not perfect and cannot be easily controlled. Let's do it right! We start with the starter: Azure Functions We have created a function that is triggered by an http request and receives information about the order. Its key element is an IDurableOrchestrationClient object that starts the selected process. It's time to use the orchestrator. In its initial simplified form it may simply look like this: Azure functions starter As you can see this is the place from which we can control the entire ordering process.
