.NET Aspire
.NET Aspire is Microsoft's orchestration model for cloud-native .NET applications. It lets you describe a multi-service system (services, databases, caches, blob storage, message brokers, external dependencies) as a typed C# app host, and have the whole thing come up locally as one piece. Service discovery, connection strings and ports are owned by Aspire rather than being copy-pasted across appsettings files.
Official WebsiteWhen to use .NET Aspire
Use Aspire when a system has more than two or three moving parts and the local development experience is starting to feel like environment-management rather than software development. It is a particularly strong fit for multi-service .NET projects with mixed dependencies (SQL, Redis, Blob storage, message queues), for teams where some developers should not have to debug docker-compose YAML to run the platform, and for greenfield projects where the local development workflow has not yet calcified.
Why choose .NET Aspire?
I describe Aspire to clients as a compile-time, type-safe alternative to Docker Compose. The app host is a typed C# project, so configuration changes are refactor-aware and IDE-aware in a way that ad-hoc YAML never is. On a recent learner platform engagement, Aspire restored a true F5 development experience across services, SQL, Blob storage and Redis from day one. Since that engagement I have used Aspire as the default local development orchestrator on every project I own.