dotnet-aspire-patterns

To orchestrate a .NET Aspire AppHost for local development, you scaffold the AppHost project to boot a local Aspire-managed topology, enforcing component wiring and service discovery across multiple projects.

Configuring service discovery and resource references in .NET Aspire involves enforcing AppHost topology to wire components together, ensuring consistent communication across distributed application projects during local dev and testing.

Adding distributed health checks and OpenTelemetry defaults to an Aspire project is handled by enforcing standardized observability rules, which automatically configure local traces, logs, and metrics for the Aspire dashboard.

You can use .NET Aspire components for backing services like databases, caches, and brokers by applying AppHost topology management to wire these resources directly into your distributed application during local development.

.NET Aspire works for building cloud-ready distributed apps by simplifying local development and service wiring, providing a managed topology that includes dashboards, health checks, and telemetry for production considerations.