Real-Time Arch for Modern ASP.NET Core Web Apps
summary
Opinionated architecture for ASP.NET Core real time apps that names concrete tools and tradeoffs it recommends using an in-memory queue before moving to external queues to avoid latency and keep real time behavior it shows Redis pub/sub as the usual backplane for scaled SignalR, suggests Azure App Service autoscale as a cheaper alternative to Kubernetes, gives a shard size example of 1,000 subscriptions and explains durable functions fan-out (now viable on the premium layer) for efficient broadcast it contrasts SignalR for browsers with gRPC for service to service and flags RSocket on Kestrel as experimental
AI-written summary · about
chapters (11)
- 0:00Start
- 1:20WebSockets
- 2:04Server-Sent Events
- 3:03Signal
- 5:33Real-Time Technologies
- 6:10Basic Connection Based Architecture
- 7:18Basic Subscription Based Architecture
- 8:17Key Abstraction: Sending
- 16:15Problem: A lot of Clients
- 29:47Change Feeds/Change Streams
- 31:51Beyond the Web
related talks
01h 00mBuilding ASP.NET Core Kestrel
01h 02mWriting high performance code in .NET
45mKeeping it Real(time)
43mUsing AI with App Service to deploy differentiated web apps and APIs
28mRealtime Content Delivery: Powering dynamic instant experiences on your mobile apps
01h 01mgRPC for ASP.NET Core, a new framework for high performance APIs
23mMoQ: Not Another Tech Demo
24mCrazy Web Performance with Azure Static Web Apps
