Build Microservices At Your Own Pace with .NET Aspire
summary
Claim: .NET Aspire packages and dashboard make it practical to adopt microservices gradually by wiring containers, observability, and deployment into C# code. It integrates OpenTelemetry for logs/traces, uses Azure Container Apps (or AKS) for hosting, generates ACD bicep and other manifests, and the demo adds a Redis cache to an eShop sample to cut repeated DB calls — showing the dashboard flip from DB hits to cache hits. Notes a striking 90% figure for teams ending in a distributed monolith; Aspire is useful but still evolving.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:39Microservices pitfalls
- 5:30A humorous take on complexity
- 10:09The distributed monolith
- 14:59Decomposition mistakes
- 20:41Tight coupling consequences
- 24:36Best practices for success
- 28:24Introduction to .NET Aspire
- 30:58Core Aspire features
- 34:30Optimizing service communication
- 39:35Progressive disclosure
- 40:59Deployment with AZD
- 42:57Hosting on Azure
- 48:51Production monitoring
- 50:04Conclusion and Q&A
related talks
40mMicroservices At Your Own Pace with NET Aspire and Azure Container Apps
51mBuild, Compose, Run Aspire and GraphQL will make you more productive
01h 12mBuilding Cloud-Native App with .NET
01h 00m.NET Aspire Beyond the Introduction
01h 01mUnleashing the Power of Microservices with Dapr and Azure Container Apps
56mTales from the trenches: Building a distributed system with Aspire and Dapr
48mBuilding Microservices Using ASP.NET Core and AKS
01h 06mFrom Core to Containers to Orchestration - Modernizing my Compute