Serverless

I had a bit of time last week to do some Dapr learning, so I started to read the Dapr for .NET Developers e-book that’s available on our documentation (completely free by the way!). In one of the early chapters, the book outlines a tutorial that you can run locally to use service invocation to communicate between to two applications. Running locally is fairly straightforward, so I wanted to deploy the two applications as Container Apps, since it has support for Dapr in the platform. ...

I’ve spent a lot of time with GitHub Actions lately and it’s been a lot of fun. I’ve had quite a bit of experience using Azure DevOps in my previous jobs and before GitHub Actions were a thing, I’d create Service Connections in Azure DevOps so that I could host my code in GitHub, but still run my build and deploy pipelines in Azure DevOps. This isn’t to say that GitHub Actions is better than Azure DevOps, nor vice-versa. This article is purely an informational piece on HOW you can use GitHub Actions to deploy your Functions to Azure. Specifically we’ll talk about: ...

In a previous blog post, I talked about how we can provision an Azure Container App using Bicep and deploying our Bicep template using GitHub Actions. We’ll now turn our attention to updating the images that our Container App uses by building the new image, deploying it to Azure Container registry and then pulling the newly built image from our registry to our Container App. As part of my infrastructure deployment, I defined a container image as part of my Bicep like so: ...

Using Bicep, we can deploy and manage all the resources required for our Azure Container Apps. In this post, we’ll write a Bicep template that defines all the infrastructure required for our Container App and deploy it using the AZ CLI. In our Bicep template, we’ll be deploying the following resources: A Log Analytics workspace. Azure Container Registry An Azure Container App Environment A Container App. Before we kick this off, it’s REALLY IMPORTANT to note that Container Apps is currently in preview! That means what I publish in my present might/will change in your future! One example of this is that the namespace that Container Apps currently reside in will be changing in March 2022, as referenced in this GitHub issue (Note to self, update this article!) ...

In Azure App Configuration, we can implement feature flags that allows us to decouple feature releases from code deployment and allows us to implement changes quickly to feature availability on demand. This allows us to test new features in production, turn features on or off without having to redeploy our code and wrap features around application functionality that we’re currently developing. There are some basic concepts to understand when working with feature management in Azure App Configuration: ...