Get up to speed with
summary
Demoed a self‑hosted traffic‑control app (camera simulator → MQTT → Dapr input binding → FineCollection) using Redis state, SMTP output binding and a vehicle‑registration service (gRPC + HTTP). Shows gRPC proxying that forwards raw proto calls via dapr-app-id metadata without changing service code, a declarative resiliency spec (timeouts, retries, circuit breaker) that turns intermittent 503s into successful 200s, content‑based routing with CEL rules and a dead‑letter topic ("unhandled") when downstream is down, an alpha configuration store (Redis key "multiplier" plus streaming updates), and a Redis‑backed distributed lock with 10s expiry scoped per Dapr app ID.
AI-written summary · about
chapters (9)
- 0:00Welcome to Dapr
- 7:15Demo traffic control app
- 10:01gRPC proxying in service invocation
- 19:19Resiliency policies
- 27:27Publish-subscribe enhancements
- 36:54Configuration for external stores
- 47:10Distributed lock for shared resources
- 52:04Further Dapr learning
- 53:47Q&A
related talks
49mDapr in Practice
56mBuilding Microservices With Dapr and .NET
30mZero to Hero with Dapr
31mBuilding scalable distributed systems powered by Dapr OSS.
31mDapr case study: Legentic
51mDay 2 Session 2
01h 19mA Match Made in The Cloud: Container Apps + Dapr
51mDapr for building distributed .NET Core applications