What problem does it solve?
It solves confusion and brittle setup when building local, cloud-native .NET systems, where developers need consistent orchestration, service discovery, observability, and infrastructure wiring.
Core Features & Use Cases
- AppHost orchestration patterns: Configure a DistributedApplication with databases, caches, and message brokers, then wire application projects via references for reliable local startup.
- ServiceDefaults for consistent infrastructure: Centralize OpenTelemetry, health checks, resilience, and service discovery so each service stays aligned without repetitive boilerplate.
- Service discovery and inter-service communication: Model service-to-service connectivity using Aspire-managed endpoints (instead of hardcoded connection strings or local host assumptions).
Use case: You are running an API plus background worker that depend on PostgreSQL and Redis, and you want tracing/health checks and reliable connectivity in local development using Aspire’s AppHost and dashboard.
Quick Start
Load the aspire skill when you start an Aspire AppHost and configure your database and cache resources, then reference them from your API and worker projects using Aspire service discovery.