He/She opens his/her favorite IDE…
On one Saturday afternoon, my wife show me a math problem from our older daughter’s math excise with a puzzled face:
Put squares together to form unique shapes.
How many solutions do 5 squares have?
This particular problem isn’t that difficult — it’s for year 4 kids after all. Kids can just draw all different combinations on a piece of paper and count the unique 12 solutions.
But what’s the pattern? What about 6 squares…
These days we can define infrastructure as code (ARM template)and CI/CD pipeline as code (YAML pipelines) in the Azure ecosystem. But why do we want to do these tasks as code?
There are good reasons apart from just a cool thing to do.
This part 4 of the series is all about retry mechanisms of Azure Durable Functions. The sample code in this story takes a very simple approach to set configurations. If you’re interested in a more sophisticated configuration set up, you may want to check out the previous story.
There are mainly 3 retry mechanisms available for durable functions.
We haven’t talked about sub-orchestrators at all in series before. It’s a very powerful feature of durable function. We will get to it, bear with me.
You may want to read the previous story of the series first if you are not familiar with Azure, or you want to explore DI options of Azure Durable Functions.
In this story, we will improve our app step by step to demonstrate various approaches to set Azure Function App configurations.
In the end, we aim to configure our function app to retrieve app settings from a fully managed configuration store and have all sensitive information protected.
Firstly, I’d like to add the configuration manager to the project so that it no longer reads configs from the environment variables directly…
Please read the first article of the series if you haven’t already.
In the second part of the series, we will:
This demo app has a simple logic: it gets a user’s repo list from GitHub, then it gets the view count of each repo, and finally, it prints the view counts. The code can be found in my GitHub repo.
The app implements the Azure Durable Function’s fan-out/fan-in pattern. …
This is the first article of this series about Azure durable functions. This series aims to provide a practical guide for devs to follow to create production-ready applications. This is a hands-on guide and it does not discuss the pros and cons of the serverless architecture.
Note: you will need to have some C# programming skills and basic knowledge of Microsoft Azure to follow along.
In this first article, we will cover:
We will build on top of this…