Did someone say event-driven architecture?

Introduction

Here we go, another brain dump to connect the dots on events in Azure. I’ve been using Event Hubs and Event Grids for a while, but one day I got stumped by the question:

“Why don’t you use Service Bus?”

And I had no answer.

We had been primarily using Event Grid, with functions subscribing directly to events. This seemed fine—Event Grid has built-in retry logic. But one day, our Azure Functions were down, and events simply dead-lettered instead of retrying. That’s when I knew I had to go deeper.

Following Up on Our Azure Deployment Journey

Introduction

In the previous post, we deployed a .NET Web API inside a Docker container and hosted it on Azure Web Apps.

That was step one—getting the app running.

Now, it’s time for step two—connecting to a database so we can persist data. This means:

• Creating an Azure SQL Database
• Configuring firewall rules so our Web App and local machine can talk to it
• Setting up the database schema with EF Core migrations
• Seeding the database with some initial data
• Verifying the connection & exposing API endpoints

If you just want the step-by-step commands to set up Azure SQL and connect it to your API, jump to the bottom for the TL;DR Deployment Guide.

A Deep Dive into Azure Web Apps, Docker, and Debugging Deployment Headaches

Introduction App

This post walks through a proof of concept (POC) where I deploy a .NET Web API in a Docker container, hosted on Azure Web Apps, using Azure Container Registry (ACR), and connected to an Azure SQL Database via Key Vault & App Insights.

I did this as part of my AZ-204 certification prep, but more than that, I wanted to fully understand the deployment process manually before automating it. That means: