Aspire isn't just for .NET — it's a polyglot orchestrator that can wire together Python, Node.js, Go, Java, and C# services under a single AppHost, with automatic service discovery, connection-string injection, and a unified observability dashboard. In this session, we'll explore that idea hands-on through seven sample applications that range from Flask and Django to Go and Java.

We'll start with how Aspire solves the polyglot problem: the service-discovery chaos, configuration fragmentation, and 15-step READMEs that plague multi-language repos. You'll see how AddPythonApp, AddNpmApp, and AddDockerfile let you bring any runtime into Aspire's lifecycle, and how environment-variable conventions replace hardcoded URLs and scattered .env files. We'll also look at OpenTelemetry integration so that distributed traces, structured logs, and metrics from every language land in one dashboard with no separate tooling per stack.

As we walk through the demos, we'll cover the practical patterns that matter most to real teams: dependency ordering, health checks across languages, connection-string injection for Redis, PostgreSQL, CosmosDB, and Kafka, and what it looks like to debug a request that crosses from a React frontend into a Go or Spring Boot backend. Finally, we'll step back and talk about the Aspire CLI workflow, what a production-ready polyglot repo looks like, and how Aspire's resource model maps to CI pipelines and
deployment automation, including where Azure fits into the picture if that's part of your story.