dotnet-aspire-patterns

Configure .NET Aspire AppHost orchestration with service discovery and OpenTelemetry observability.

10|Updated Jan 28, 2026

Search Tags:#orchestration #observability #distributed systems #service discovery #apphost #.net aspire

Ready to run

npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-aspire-patterns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-aspire-patterns
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-aspire-patterns
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-aspire-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the development and orchestration of distributed .NET applications by providing standardized patterns for service discovery, observability, and resource management.

Core Features & Use Cases

AppHost Orchestration: Define your application topology in C# for local development.
Service Discovery: Enables services to find and communicate with each other automatically.
Observability: Integrates OpenTelemetry for logging, tracing, and metrics, with a built-in dashboard.
Component Model: Simplifies integration with backing services like databases and caches.
Use Case: Develop a microservices-based application with multiple .NET services and backing databases, ensuring consistent logging, tracing, and easy local debugging through a unified dashboard.

Quick Start

Use the dotnet-aspire-patterns skill to create a new .NET Aspire application with a React frontend.

Frequently Asked Questions about dotnet-aspire-patterns

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

FAQPage Schema

How do I orchestrate distributed .NET microservices for local development?▼

.NET Aspire orchestration uses an AppHost configuration to define your application topology in C#, simplifying local development and standardizing cross-cutting concerns for distributed services. It enables service discovery and built-in dashboard observability.

What is the best way to add health checks and tracing to .NET microservices?▼

Adding health checks and tracing to .NET microservices is handled through .NET Aspire's observability model. It integrates OpenTelemetry for logging, tracing, and metrics, and provides a built-in dashboard for easy local debugging.

How does service discovery work in .NET Aspire distributed apps?▼

Service discovery in .NET Aspire distributed apps works automatically by enabling services defined in the AppHost to find and communicate with each other. This simplifies orchestration and standardizes cross-cutting concerns for local development.

Can I use .NET Aspire patterns to integrate backing services like databases and caches?▼

Yes, you can integrate backing services like databases and caches using .NET Aspire's component model. It simplifies integration with these resources to build observable, production-ready distributed applications with consistent logging and tracing.

Do I need .NET Aspire to standardize cross-cutting concerns for my microservices?▼

You need .NET Aspire when developing a microservices-based application with multiple .NET services and backing databases. It standardizes cross-cutting concerns like service discovery, observability, and resource management for production-ready apps.

When should I not use .NET Aspire orchestration patterns for app development?▼

.NET Aspire orchestration patterns are designed for distributed applications with multiple .NET services and backing databases. You should avoid this approach for simple, single-service applications that do not require standardized service discovery or distributed observability.