Making Static Dynamic - Adding SignalR to Azure Static Web Apps
summary
Shows how to add real‑time updates to an Azure Static Web Apps + Blazor Wasm site by wiring Azure Functions to Web Pub Sub (not SignalR), generating a short‑lived connection URI on the server, and running a websocket client in the browser. Demonstrates the four-line send call, HTTP endpoints for send to user or group, client-side connect/disconnect and event handlers, local SWA CLI testing, free‑tier limits (~20 concurrent, 50k messages) and a Cosmos DB trigger demo for book‑library notifications.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 4:39Real-time updates for static apps
- 6:24Web PubSub setup
- 7:53Web PubSub endpoint
- 10:26Message sending function
- 13:44Client Web PubSub service
- 18:19Blazor service integration
- 19:50Sign-in and homepage
- 24:55Sending messages to all users
- 27:04User/group messaging
- 30:37Group messaging
- 34:15Live demo
- 35:47Book tracking use case
- 38:36Cosmos DB triggers
- 41:03Watched items notifications
- 42:50Security considerations
- 44:15Testing the demo
- 46:25Summary
related talks
01h 01mEvent driven applications in Azure
52mAzure CosmosDB, Azure Function, Azure SignalR Service&Blazor
28mBuild Serverless Apps with Blazor
46mAzure Static Web Apps - From Zero to Deployed App In 60 Minutes
57mBuilding a real-time serverless app in Blazor using AWS
19mHow Static Web Apps saved time and money!
01h 01mBuilding a real-time serverless app in Blazor using AWS
01h 01mGo Serverless with Cosmos DB, Azure Functions and Blazor
