.NET Aspire and AWS: a match made in heaven
summary
Demonstrates a workflow that starts from a Blazor UI and with one solution adds instrumentation, provisions AWS resources via CDK, and runs everything locally so an F5 debug provisions AWS resources. Uses Visual Studio Aspire apphost, automatic OpenTelemetry traces across services, SNS + SQS + DynamoDB created by CDK, the .NET object persistence model to save orders, the Message Processing Framework for publish/subscribe, and Amazon Comprehend for sentiment. Example scales to a chain of 81 locations with end-to-end traces and structured logs.
AI-written summary · about
chapters (15)
- 0:00.NET Aspire & AWS intro
- 1:48.NET Aspire for cloud-native
- 3:16Oddball Pizza modernization
- 8:13Instrumenting with .NET Aspire
- 10:43Blazor frontend
- 14:41DynamoDB for menu
- 21:07SNS & SQS messaging
- 29:59DynamoDB for orders
- 34:47Kitchen store interface
- 41:04AI sentiment analysis
- 50:02Production deployment
- 52:09Multi-region scaling
- 53:38Cleanup with CDK
- 57:43Demo recap & takeaways
- 59:27Q&A: Debugging & scaling
related talks
02h 33m.NET Aspire: Let's build a cloud application with baked in observability
01h 01mSupercharging Local Development with Aspire
28mDapr and .NET Aspire - A New Era for Observability
44mCloud-native development with .NET 8
01h 01mLogging, tracing and metrics: instrumentation in .NET and Azure
40mOptimizing AI Applications for Production with Observability
01h 00mDon't Fly Blind - Implementing Effective Application Instrumentation
33mProfile & Monitor Web Apps with Azure Application Insights