Dapr in Practice
summary
Dapr (Distributed Application Runtime) runs as a sidecar alongside app containers and exposes building blocks via HTTP/gRPC so code calls a consistent API while components implement concrete services (example: pubsub with SNS/SQS). About 90% of installs run on Kubernetes. Components live in YAML with scoped access control; runtime supports state stores, encrypted service invocation, and durable workflows (example: 60s pickup timer that resumes on restart). Operational work includes component provisioning (Crossplane), management tooling (Conductor) and writing pluggable components for unsupported systems.
AI-written summary · about
chapters (14)
- 0:00Introduction to Dapr
- 1:31Setting the stage for distributed applications
- 7:36Dapr overview
- 14:18Dapr control plane
- 18:10Pub/Sub messaging
- 22:00Portable apps with Dapr
- 25:11Event modeling
- 29:02Dapr workflows
- 31:53Custom Dapr components
- 36:59Location transparency
- 40:11SQL gaps in Dapr
- 42:45Abstraction layers limits
- 45:11Dapr provisioning
- 49:26Dapr adoption feedback
related talks
46mDistributed Application Runtime
46mDapr in Practice
31mBuilding scalable distributed systems powered by Dapr OSS.
21mShaping next generations of architectures with Dapr
37mStart building distributed applications with ease using building block APIs
36mA Guide to Dapr: Open Source APIs & SDKs for Developers
49mStart Building Distributed Applications with Ease Using Building Block APIs
57mDeveloping microservice applications with Dapr