Dapr in Practice
summary
Dapr presents concrete building blocks—pubsub, service invocation, state management—exposed via a sidecar that translates HTTP/gRPC to pluggable components (SNS/SQS, Kafka, Postgres, Axon) so application code only calls a standardized API. Deployments run mostly on Kubernetes (claimed ~90%), use mTLS between sidecars, OpenTelemetry for traces, and Crossplane/Argo-style tooling to provision component resources. The bike-rental example shows Dapr Workflows and bindings wired to an event store; it works but forces platform provisioning and occasional bespoke components for uncovered cases.
AI-written summary · about
chapters (15)
- 0:00Introduction to Dapr
- 1:11Setting the stage for distributed applications
- 3:19Why Dapr for messaging
- 6:26Dapr runtime overview
- 10:20Standardized APIs
- 13:51Pub/sub example
- 17:00Service invocation
- 20:41Bike rental architecture
- 24:51Dapr workflows
- 26:58Custom components
- 31:41Messaging types
- 33:47Dapr limitations
- 37:42Dapr and platform engineering
- 42:06Developer benefits
- 45:41Q&A
related talks
31mBuilding scalable distributed systems powered by Dapr OSS.
56mBuilding Microservices With Dapr and .NET
51mDay 2 Session 2
31mDapr case study: Legentic
30mDapr case study: Man Group
04mProject Lightning Talk: Dapr: Start Building Distributed Applications with Ease Using Building Block APIs
45mDapr Workflows: How to Write Reliable, Fault-Tolerant Applications...
29mRunning Dapr in Production