1 Getting started with distributed systems and Aspire

Distributed applications are much harder to run locally than a single-process app because they are made of independently running parts that all need to be started, configured, and kept in sync. The chapter uses an online shop to show how a storefront, API, database, cache, message broker, and background services cooperate as one system, even though each piece is separate and can fail, start slowly, or depend on something else being ready first.

To reduce that complexity, Aspire provides a code-first way to describe the whole application as a model centered on an AppHost project. From that single host, developers can start resources together, pass configuration and connection details, manage dependencies, discover services without hardcoded addresses, and see logs, state, and telemetry in one dashboard. The chapter emphasizes that Aspire does not merge services into one executable; it helps coordinate and observe them while they remain independent.

The first working example introduces a simple storefront and catalog API, then shows how the host application registers those projects, waits for readiness, and connects them through service discovery. It also introduces service defaults, which package shared setup such as health checks, telemetry, and discovery support into reusable code. By the end, the reader has a practical foundation for building, debugging, testing, and eventually evolving a realistic cloud-native system with Aspire.