An infrastructure resource is a supporting component that an application service depends on, such as a database, distributed cache, or message broker. In an online shop, the catalog API needs a database and cache, while checkout publishes messages to a broker. These components must run alongside the services that use them. section 1.0
Aspire’s AppHost provides a code-first place to declare services, infrastructure resources, and their relationships. Aspire can then start resources together, supply connection information, coordinate dependencies, and show resource state and telemetry in a shared dashboard. The services remain independent applications. section 1.0
Infrastructure components can be connected to an Aspire application in two ways:
- Use Docker containers, such as a Keycloak container for security infrastructure. section 2.0
- Use Aspire integration libraries, including a prebuilt Redis integration or a custom integration library. section 2.0
Moving an existing application to Aspire can also mean moving its databases and message brokers into the Aspire model. Existing components can be converted to Aspire integrations while their production versions remain intact. section 10.0
