aspire-orchestration

Orchestrate .NET microservices with service discovery and local emulators.

4|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill aspire-orchestration-faysilalshareef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-orchestration
Source: https://github.com/FaysilAlshareef/dotnet-ai-kit/tree/main/skills/devops/aspire-orchestration
Command: npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill aspire-orchestration-faysilalshareef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local .NET development often requires manual coordination of multiple microservices, emulators, and observability settings which leads to inconsistent environments, hardcoded endpoints, and wasted setup time. Aspire Orchestration provides a repeatable approach to define service topology, automate resource emulation, and enable service discovery so developers can run a realistic local environment that mirrors production behaviors.

Core Features & Use Cases

  • AppHost Topology: Define microservice topology and inter-service references in a centralized AppHost project to orchestrate services consistently.
  • ServiceDefaults: Share telemetry, health checks, HTTP client defaults, and service discovery configuration across services to ensure consistent observability and resilience.
  • Local Emulators & Discovery: Provision SQL Server, Cosmos DB, and Service Bus emulators and replace hardcoded URLs with service discovery for reliable local testing.
  • Use Case: Stand up an Order domain locally with Command, Query, Processor, and Gateway projects that use shared ServiceDefaults and emulated infrastructure for end-to-end testing.

Quick Start

Create an Aspire AppHost, add ServiceDefaults for telemetry and health, provision SQL and Service Bus emulators, and register your Command, Query, Processor, and Gateway projects so the local environment runs end-to-end.

Frequently Asked Questions about aspire-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate local .NET microservices for development without hardcoding endpoints?

You orchestrate local .NET microservices by defining service topology in a centralized Aspire AppHost and using ServiceDefaults to replace hardcoded URLs with service discovery for reliable local testing.

What is .NET Aspire ServiceDefaults used for in local microservice development?

.NET Aspire ServiceDefaults shares telemetry, health checks, HTTP client defaults, and service discovery configuration across microservices to ensure consistent observability and resilience during local development.

How do I provision SQL Server, Cosmos DB, and Service Bus emulators for .NET local testing?

You provision SQL Server, Cosmos DB, and Service Bus emulators by configuring them within an Aspire AppHost project, which automates resource emulation for your local microservice environment.

Can I use .NET Aspire to connect Command, Query, Processor, and Gateway projects locally?

Yes, .NET Aspire can register and connect Command, Query, Processor, and Gateway projects in an AppHost, allowing your local environment to run end-to-end with shared ServiceDefaults and emulated infrastructure.

Does .NET Aspire orchestration support OpenTelemetry instrumentation and health endpoints out of the box?

.NET Aspire orchestration supports OpenTelemetry instrumentation and health endpoints by applying shared ServiceDefaults across your microservices, satisfying standard observability requirements for local testing.

Why should I use .NET Aspire instead of manually coordinating local microservices and emulators?

Manually coordinating microservices leads to inconsistent environments and wasted setup time, whereas .NET Aspire provides a repeatable approach to define topology, automate emulation, and enable service discovery for a production-like local environment.