Tales from the trenches: Building a distributed system with Aspire and Dapr
summary
A government project with €3M in one year uses .NET Aspire for local developer orchestration and Dapr as a runtime sidecar for service invocation and state; Aspire cuts onboarding to a single git clone F5 while Dapr adds gRPC hops and transparent service discovery. Constraints force Terraform for landing zones that change twice, Preview upgrades require days to fix, migrations run as init containers, and Dapr hides some exceptions so tracing and logging become essential.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:06Project overview
- 2:30Customer constraints
- 7:48Dapr and Aspire intro
- 13:11Project architecture
- 15:20Dapr sidecar pattern
- 21:02Live Dapr demo
- 24:44Aspire setup
- 29:49Aspire dashboard
- 33:07Dapr with Aspire
- 40:40Dapr config flexibility
- 42:29Aspire dashboard features
- 44:11Dapr vs Aspire overlap
- 45:16Database migrations
- 47:02App host Terraform
- 48:47Developer onboarding
- 49:30Terraform workflow
- 51:58Container deployment
- 53:24Infrastructure workarounds
- 53:45Conclusion and key takeaways
related talks
21mShaping next generations of architectures with Dapr
22mBuilding Real-World Applications with Dapr: A Startup Developer's Journey
31mBuilding scalable distributed systems powered by Dapr OSS.
37mStart building distributed applications with ease using building block APIs
01h 03mPostponing architectural choices and start developing first with Dapr
01h 06mBuild powerful distributed applications with Dapr and .NET
57mDeveloping microservice applications with Dapr
54mDapr in Practice