In this post, I will show you how to create a Blazor C# WebAssembly app with a serverless backend utilizing Azure Functions. The data will be persisted to Azure Tables, Blobs and Files Shares in the Azure Storage Account which will also be used to host the backend functions and frontend as a static web page. Finally, we’ll make a CI/CD pipeline to deploy our app.
In this code snippet, we will look at Durable Azure Functions. Azure functions are stateless by default. But we can add state by using the Durable Functions extension. This allows you to implement common patterns such as Function chaining, Fan-out/fan-in, Async HTTP APIs, Monitoring, Human interaction, Aggregator.
In this post, I will show you how to properly use the C# Http Client in Azure Functions using dependency injection(the same concept applies to other C# .NET technologies). I’ll also show you how to add request caching to improve performance.
In this post, we’ll talk about bindings and triggers in Azure Functions. In my other post “Getting Started With C# Azure Functions” where I show how to create a basic function I added an Http Trigger when creating the project. Here I’ll show you how to add additional triggers and bindings to your function.
In this code snippet, we will learn how to queue, check and dequeue messages from Azure Queues using C#.
In this code snippet, we will learn how to read, write and delete files in Azure Blobs(binary large object) using C#. Additionally, I’ll show you how to get the URL for a file and how to generate a SAS(shared access signature) token for it which can be used to download the file.
In this code snippet, we will learn how to read, write and delete files to Azure File Shares using C#. Additionally, I’ll show you how to get the URL for a file and how to generate a SAS(shared access signature) token for it which can be used to download the file.
In this code snippet, we will learn how to read and write to Azure Tables using C#. Azure Tables are great for large amounts of nonstructured(NoSQl) schema-less data. The data is stored as key-value pairs.
In this post, I’ll show you how to set up a CI/CD(continuous integration and continuous delivery/deployment) pipeline in Azure DevOps for Azure Functions running on Azure cloud.
In this post, I’ll show you how to prevent your Azure Functions from going to sleep thus preventing a cold start and improving the response time of the first call. This can be especially important if you have multiple function chained because you now have multiple cold starts in a row.