When a DAPR App Doesn't Behave as Expected in Container Apps Services
summary
Demonstrates two Dapr-based replicas: one uses Dapr query-state (alpha) with Cosmos DB for state reads, the other uses Dapr bindings to upload large files to Azure Blob Storage. Shows concrete tooling (Bicep, ACR, Key Vault, App Registration), explains a Container Apps error “State Store is not configured” caused by a gRPC connection race (workaround: restart the revision), and fixes an 8 MB limit by increasing HTTP max request size and container configuration.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 5:23What is DAPR and features
- 10:10DAPR issues in Container Apps
- 13:19Demo: Q State example
- 39:42Setting up components
- 56:34Fixing 500 error
- 1:03:03Demo: Block Storage files
- 1:17:50Scaling large files
- 1:25:19Summary & Q&A
related talks
01h 03mDeveloping microservices like a boss with Dapr and Azure Container Apps
01h 01mUnleashing the Power of Microservices with Dapr and Azure Container Apps
54mDapr in Practice
01h 03mPostponing architectural choices and start developing first with Dapr
20mEnhancing Workflow Reliability with Dapr
39mDeploy to the cloud at lightning speed with .NET Aspire and Azure Container Apps
01h 07mDocker Containers on Azure - let me count the ways
47mDeveloping .NET Apps using Azure Developer CLI (azd)