As a .NET developer, you will have either built distributed apps or heard about them. Distributed apps, microservice or not, come with a new set of complexities that you previously didn't have to deal with. However, those complexities are easily embraced by setting up a good local development environment.

This is where Dapr and .NET Aspire come in.

Dapr allows you to abstract infrastructure away from your app code, allowing you to focus on writing your business logic and let Dapr deal with connecting to things like Message Brokers, State Stores and other services .NET Aspire then orchestrates all those dependencies during local development, connecting them all together seamlessly and then, during runtime, providing a single pane of glass to observe your applications' behaviour.

This session will show you how to set up your local environment, whether this is via Rider or Visual Studio. We will use a demo app to demonstrate the different abstractions that Dapr offers and how to integrate them with multiple services running locally on your development machine.

Then, we will explore the different ways in which Aspire collects logs, traces and metrics via OpenTelemetry. You can use this to see how your different services interact and where issues in your apps occur. We will even go as far as creating custom metrics and traces that will enhance the capabilities of OpenTelemetry even further.

Lastly, we will discuss what will happen when you deploy your application. There are multiple compute options that support Dapr natively, such as Azure Kubernetes Service and Azure Container Apps. However, there are more options that we will also cover.