Skip to main content

Create a Durable Azure Function with Visual Studio

First, let's talk about the difference between an Azure Function and a Durable Azure Function. The difference here is stateful vs stateless. A stateless platform does not hold your data. A stateful platform does hold your data.

To give a few examples, Docker containers are stateless. Once that container is gone, the data is gone. This is why (besides performance issues) it's frowned upon to put databases in containers (sure, you can mount volumes for the purpose of making it stateful, but that's off topic). However, LXC (Linux Containers) are stateful and hold your data.

Another example is your computers RAM and hard drive. RAM is stateless, meaning once you turn off your computer, everything held in RAM is gone. However your hard drive is stateful, as in once your computer gets turned off, your data stored in your hard drive still exists.

Now that we understand stateful vs stateless, let's talk about Azure Functions. Durable Azure Functions are "stateful". Let's go ahead and create one.

Pre-requisites;
1. An Azure account
2. Visual Studio (Community works fine)
3. The Azure Development Visual Studio extension. If you do not have this, if you get the executable for Visual Studio and run it, it'll give you an option to add extensions.


Let's go ahead and open up a new Visual Studio project by creating a new project. under Azure Resource Group templates, choose Azure Functions.


Give your app a name and click Create.


For the next part, we can use an empty function with no triggers. If you look on the right side, you'll see "Storage Account (AzureWebJobsStorage).


Click on the drop-down and choose "Browse...". You'll see an Azure Storage window where you can create a new or existing storage account. Go ahead and create a new storage account. I'm going to call mine "mjlapp92storage". I'll choose my subscription, resource group, location, and account type. After you click create, go ahead and click add.



Click create.

Now that my app is created, I'm going to add the Durable Functions Orchestration by right clicking my app clicking Add > New Azure Function. Ensure that you choose Azure Functions.



Under the function, choose the "Durable Functions Orchestration" option and click OK.



Once that is complete, I'm going to right click my app and choose "Publish" so I can publish my function app to Azure.


Click start and under the consumption plan, choose "Create new".


Click the publish button, confirm your settings, and click "create".



Once the deployment is complete, head over to your Azure portal and go to Azure Functions.


Click on your function app and click on the URL. You should see a function app splash page. Every time someone accesses this URL, your state will be saved.


If you head over to your storage account, you'll see that your "state" of your application is being saved.


You now have a stateful Azure function! Thanks for reading.

Comments

Popular posts from this blog

Run PowerShell code with Ansible on a Windows Host

Ansible is one of the Configuration Manager kings in the game. With it's easy-to-understand syntax and even easier to use modules, Ansible is certainly a go-to when you're picking what Configuration Management you want to use for your organization. Your question may be "but Ansible is typically on Linux and what happens when I'm in a Windows environment?". Luckily I'm here to tell you that Ansible will still work! I was pleasantly surprised with how easy it is to use Ansible on Windows with a little WinRM magic. Let's get started.

Pre-requisites for this post:
1) WinRM set up to connect to your Windows host from Ansible
2) Ansible set up for Windows Remote Management
3) SSH access to the Ansible host
4) Proper firewall rules to allow WinRM (port 5985) access from your Ansible host to your Windows host
5) Hosts file set up in Ansible that has your IP or hostname of your Windows Server.
6) At least one Linux host running Ansible and one Windows Server host …

Running PowerShell commands in a Dockerfile

As Docker continues to grow we are starting to see the containerization engine more and more on Windows. With the need for containers on Windows, we also need the same automation we get in Linux with Dockerfiles. Today we're going to create a Dockerfile that runs PowerShell cmdlets.
Prerequisites; 1. Docker for Windows
2. A code editor (VSCode preferred)

Let's go ahead and get our Dockerfile set up. Below is the Dockerfile I used for this post.

from mcr.microsoft.com/windows/servercore:1903 MAINTAINER Michael Levan RUN powershell -Command Install-WindowsFeature -Name Web-Server RUN powershell -Command New-Item -Type File -Path C:\ -Name config
As you can see from the above, this is a tiny Dockerfile. What this will do is install the IIS Windows 

Feature and create a new file in C:\ called "config".
You should see something very similar to the below screenshot;

Next let's create a running container out of our image. First we'll need to run docker container ls to

 get o…

DevOps tooling in the Microsoft realm

When I really started to dive into automation and practicing DevOps with specific tooling, there were a few key players. At the time Microsoft was not one of them. They were just starting to embrace the open source world, including the art and practice of DevOps. Since then Microsoft has went all in and the tech giant has made some incredible tooling. Recently I switched to a Microsoft-heavy environment and I love it. I went from AWS/Python/Ansible/Jenkins to Azure/PowerShell/ARM/Azure DevOps. My first programming language was PowerShell so being back in the saddle allowed me to do a full circle between all of the different types of tooling in both worlds. Today I want to share some of that tooling with you.

The first thing I want to talk about is ARM. What is ARM? ARM is a configuration management tool that allows you to perform software-defined-infrastructure. Much like Ansible and Terraform, ARM allows you to define what you want your environment to look like at scale. With ARM, yo…