Dapr in Practice
summary
Dapr provides language-agnostic building blocks (pub/sub, service invocation, state, bindings, workflows) via a sidecar and standard HTTP/gRPC APIs, with components like AWS SNS+SQS offering at-least-once delivery and CloudEvents formatting. It leaves resource provisioning to tools like Crossplane, so platform teams create databases and inject credentials into Dapr components. Example: a bike-rental workflow uses state + pubsub + bindings and a durable workflow engine; covers roughly 85–95% of common needs, with custom components for the rest.
AI-written summary · about
chapters (15)
- 0:00Introduction to Dapr
- 1:50Dapr architecture
- 3:15Messaging with Dapr
- 9:03Pub/Sub and AWS SNS/SQS
- 12:00Decoupling cloud apps
- 15:11Service invocation patterns
- 18:04Portable apps with Dapr
- 19:27Event modeling
- 23:06Dapr workflows
- 26:00Workflow engine
- 28:31Custom components
- 32:25Unsupported use cases
- 35:16Dapr and Crossplane
- 40:19Key takeaways
- 41:41Q&A
related talks
54mDapr in Practice
57mDeveloping microservice applications with Dapr
46mDistributed Application Runtime
22mBuilding Real-World Applications with Dapr: A Startup Developer's Journey
21mShaping next generations of architectures with Dapr
31mBuilding scalable distributed systems powered by Dapr OSS.
28mOpening keynote
37mStart building distributed applications with ease using building block APIs