One Step Deeper in Dapr's Pub:Sub
summary
Dapr runs as a sidecar per app and handles all broker plumbing so publishers call HTTP POST /v1.0/publish/{pubsub}/{topic} and subscribers expose a JSON endpoint that Dapr calls. It supports Redis and RabbitMQ interchangeably by changing config only, wraps messages as CloudEvents wrapper optional (metadata: rawPayload), and routes messages with rule expressions using the Common Expression Language to different HTTP routes. Dapr also supports TTL, dead‑lettering, and competing consumers via app_id.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:29How Does Dapper Really Work
- 4:12State Management
- 5:45The Benefits
- 6:15Secret Management
- 16:10Visual Studio Code
- 17:13Node Subscriber
- 43:50Final Thoughts
- 46:00Challenges
related talks
58mAsync messaging deep dive with Dapr, take your pub/sub skills to the next level 📨🚀
31mBuilding scalable distributed systems powered by Dapr OSS.
56mBuilding Microservices With Dapr and .NET
46mDapr in Practice
36mA Guide to Dapr: Open Source APIs & SDKs for Developers
57mDeveloping microservice applications with Dapr
46mDistributed Application Runtime
54mDapr in Practice