Build Scalable Web Apps with .NET and Azure
summary
An on-prem ASP.NET MVC concert app is lifted to Azure and rearchitected: code deploys to Azure App Service, secrets move from app settings into Key Vault and App Configuration, cache is added with Azure Redis, and user auth uses Azure AD B2C. A storage queue plus Azure Functions generates ticket images into Blob storage, tied to SQL rows, and access uses Managed Identity so no connection strings circulate. Front Door provides CDN, geo-routing and failover; the demo shows the queue-and-function flow successfully producing images.
AI-written summary · about
chapters (24)
- 0:00Start
- 1:44Resiliency
- 12:58Deploy It to an Azure Web App Service
- 13:27Multi-Language Support
- 14:29Why Key Vault
- 16:00Add in the Nugets for Key Vault
- 16:39Key Vault
- 17:11Sql Server Connection String
- 18:57Create a Key Vault Version into the App Config
- 20:45Default Azure Credential
- 28:13Manage Identity
- 30:52Azure App Config
- 34:20App Config Url
- 35:56App Config
- 37:58Redis Cache
- 46:17App Registrations
- 46:55User Flows
- 48:21Company Branding
- 49:49Api Permissions
- 52:05Sql Database
- 53:07Asynchronous Tasks
- 53:52Why Azure Functions Responds to Triggers of Various Types
- 59:49Azure Front Door
- 1:03:39Set Up a Authentication a Redirect Url
related talks
37mRunning SaaS multi-tenant applications on ASP.NET Core, Azure
44mFive Cloud Services Every Developer Should Know
01h 01mFive Azure services every developer should know
58mAdvanced Azure App Services
45mModernize .NET and Java web apps in Azure App Service
01h 01mAzure Network Security
36mCloud First Web Apps in Azure
01h 01m5 Azure Services Every .NET Developer Needs to Know