Dapr for building distributed .NET Core applications
summary
A working Twitter leaderboard for hashtag microsoft runs end to end using .NET Core 3.1 and Dapr: a local dapr CLI + Docker Desktop composition injects a sidecar architecture that binds to Twitter, publishes events to Azure Service Bus, stores state in Redis, and pushes UI updates via Azure SignalR. The demo uses Dapr input/output bindings, the actor programming model to keep per‑tag top‑10 leaderboards, and Dapr client SDK calls; everything boots, receives tweets, updates actors, and the UI refreshes without polling.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:28Agenda
- 4:37Sidecar architecture
- 5:21Running Dapr in Kubernetes
- 6:40Dapr API
- 7:24Dapr Components
- 10:04Getting up and running
- 11:13Running Dapr locally
- 12:33Dapr Builder Extensions
- 13:25Twitter Monitor
- 15:01Twitter Monitor Code
- 23:23Publishing
- 25:33State Storage
- 26:41NetCore SDK
- 27:17Demo
- 27:43Message Bus
- 35:57Leaderboard
- 43:28Notifications
- 49:00Conclusion
related talks
01h 03mDapr for building distributed .NET Core applications
01h 06mBuild powerful distributed applications with Dapr and .NET
56mBuilding Microservices With Dapr and .NET
31mBuilding scalable distributed systems powered by Dapr OSS.
57mDeveloping microservice applications with Dapr
37mStart building distributed applications with ease using building block APIs
01h 19mA Match Made in The Cloud: Container Apps + Dapr
46mDistributed Application Runtime