# Aspire 13: One AppHost, Many Languages, Fewer Headaches? - Chris Ayers - NDC Toronto 2026

## Executive summary

Aspire AppHost provides a unified orchestration layer for polyglot systems, allowing developers to treat mixed-stack projects (e.g., .NET API, Python worker, Node front end) as a single product rather than multiple disconnected repositories. The system simplifies local development by automating service wiring, managing configuration via environment variables, and providing a centralized dashboard for unified telemetry, logging, and debugging across diverse languages.

## Key takeaways

- Unified Polyglot Orchestration: Aspire AppHost allows developers to declare services, dependencies, and resources in one place, eliminating the need for scattered configuration files (YAML, appsettings.json) and complex manual setup scripts.
- Centralized Observability: The dashboard provides a single pane of glass to view telemetry, structured logs, traces, and metrics from all connected services, greatly simplifying debugging across different language stacks.
- Automated Service Wiring & Discovery: Service discovery is handled automatically using conventions (e.g., `services_` or `connections_`), ensuring that services can find and connect to dependencies (like databases) without manual IP/port configuration.
- AI-Assisted Development Workflow: New agent capabilities allow developers to manage environments, query logs, debug failures, and even suggest code fixes directly within the chat interface (e.g., using VS Code Copilot).

## Technical details

- AppHost Structure: The AppHost file is the core component where services, dependencies (e.g., Redis, PostgreSQL), and resources are declared. It manages configuration injection and monitoring consistently across all integrated languages.
- Cross-Language Support: Aspire supports multiple language stacks including C#, TypeScript, Python, Node, Go, Java, and is expanding rapidly. The goal is to provide a consistent development model regardless of the component's underlying language.
- CLI Tooling: The Aspire CLI provides commands for managing the workflow, including `aspire run` (to start/debug), `aspire test`, and `aspire secrets list` (for secret management). It also supports running in detached mode.
- Deployment Flexibility: Aspire can orchestrate local emulators (e.g., Cosmos DB, Redis), connect to live cloud resources (Azure/AWS links), and integrate with container runtimes like Docker Compose and Kubernetes.

## Practical implications

- Reduces development toil associated with setting up and maintaining complex polyglot environments.
- Streamlines the transition from local development to CI/CD by providing a consistent model for service wiring and configuration management.
- Enables easier debugging in large, distributed systems by centralizing logs and metrics into one dashboard.
- Facilitates team onboarding by standardizing the process of running and testing multi-language applications.

## Topics

Polyglot Development, Microservices Architecture, DevOps Tooling, Containerization, Observability, Build Automation, Aspire AppHost, Aspire CLI, aspire.dev

Source: https://www.youtube.com/watch?v=TCw5-pLMW-0