Event driven applications in Azure
summary
Shows a concrete serverless design: an HTTP negotiate function returning SignalRConnectionInfo issues short-lived tokens that clients use to open duplex websockets to a serverless Azure SignalR Service (tiers: 1k connections/unit, up to 100 units, ~1M messages/unit). Demo uses Azure Functions for an API (post /talk queues messages) and a tiny single-page client, deployed with Static Web Apps + GitHub Actions staging per PR so index.html and functions publish together. Production example is Timekeeper, used on Learn TV / Hello World, with authenticated host roles to start/stop synchronized countdowns and color/alert messages.
AI-written summary · about
chapters (28)
- 0:00Start
- 0:19Welcome
- 1:43Agenda
- 2:53Timekeeper
- 4:08Latency
- 6:51Web Sockets
- 8:08Websocket Secure
- 8:37Azure Signalr
- 13:55Chat Server
- 15:25Http Triggered Function
- 17:09Binding
- 21:28Create a New Resource
- 22:45Pricing Tier
- 25:49Local Settings Json
- 26:21Key Vault
- 30:04Css Transitions
- 31:29Add the Javascript Packages
- 34:31Hub Connection Builder
- 36:44Deployment
- 37:17Free Plan
- 38:16Custom Authentication
- 38:50Staging Environment
- 39:45Azure Functions
- 41:31Create a New Repo
- 46:05Static Web Apps
- 51:57Humans of Microsoft
- 53:56Role Management
- 1:00:09Summary
related talks
33mRealtime web applications, from your Mac to the Cloud, with SignalR and Azure
39mIntroducing Azure Functions for serverless .NET
47mMaking Static Dynamic - Adding SignalR to Azure Static Web Apps
01h 01mServerless Architecture With Azure
47mThousands of concurrent connections with Azure SignalR Service
46mBuild serverless, full stack applications in Azure with Azure SQL
51mServerless – are you ready for the revolution?
54mUnderstanding the Serverless platform in Microsoft Azure