How azure-samples/dotnet-frontend-to-backend-with-dapr-on-azure-container-apps works
Project type and purpose
• This is a cloud-native full-stack application built with ASP.NET Core 6.0
• It consists of a Blazor Server front-end (“Store”) and two minimal back-end microservices (Products API and Inventory API)
• It is deployed to Azure Container Apps, with infrastructure defined in Bicep and CI/CD managed by GitHub Actions
File structure
• Top-level “Store” folder contains the Blazor Server UI (Program.cs, App.razor, Pages, Shared, wwwroot)
• “Store.ProductApi” and “Store.InventoryApi” are two separate minimal API projects, each with a Program.cs, Dockerfile, appsettings, and .csproj
• “Azure” folder contains Bicep templates (container_app.bicep, environment.bicep, main.bicep) used to provision Azure Container Apps Environment, container apps, ACR, Log Analytics, Application Insights
• GitHub Actions workflow under .github/workflows/deploy.yml defines the CI/CD pipeline (provision, build, deploy phases)
• Monitoring folder holds instrumentation code for Application Insights
README for additional insights
• Confirms the front-end uses Blazor Server to display product names (from Products API) and inventory counts (from Inventory API)
• Back-end APIs are internal-only (no public ingress) and are called by the server-side Blazor code