Abstracting My Distributed Architecture? Why and How?
summary
Introduces Dapr as a way to reduce developer cognitive load when managing distributed architectures. Covers common distributed-system concerns—logging, service resilience, connections to message brokers, databases and REST services, observability, security and service discovery—and demonstrates Dapr through live coding to show how it can simplify those integrations so developers can focus on features.
AI-written summary · about
chapters (15)
- 0:00Abstraction introduction
- 1:48Microservice issues
- 5:22Distributed complexity
- 8:33Why abstract architecture
- 11:01Dapr overview
- 15:42Dapr architecture
- 17:51Q&A before demo
- 18:12Demo with RabbitMQ
- 22:03Migrating to Dapr
- 30:09Migrating to Kafka
- 34:06Q&A
- 40:32API strategy
- 41:57Testing with Dapr
- 44:10Dapr features
- 45:20Progressive migration
related talks
40mDistributed Application Runtime: To Be or Not To Be
31mBuilding scalable distributed systems powered by Dapr OSS.
49mDapr in Practice
56mBuilding Microservices With Dapr and .NET
04mProject Lightning Talk: Dapr: Start Building Distributed Applications with Ease Using Building Block APIs
51mDay 2 Session 2
31mThe Dapr Actors Journey: From Understanding to Intuition
31mDapr case study: Legentic