Replaced .NET Aspire components with integrations.

Author: alistairmatthews

docs/architecture/distributed-cloud-native-apps-containers/Aspire ebook asset creation.pptx

@@ -147,7 +147,7 @@ Another advantage of the Azure SignalR Service comes with implementing serverles
 
 Azure SignalR Service closely integrates with other Azure services, such as Azure SQL Database, Service Bus, or Azure Redis Cache, opening up many possibilities for your cloud-native applications.
 
-If you're using the .NET Aspire stack to build your cloud-native app, you have a built-in .NET Aspire component that helps you call the Azure SignalR Service. This component takes care of creating the connection and makes it easy for microservices to locate it. You can easily add connections from microservices and use them to send and receive information.
+If you're using the .NET Aspire stack to build your cloud-native app, you have a built-in .NET Aspire integration that helps you call the Azure SignalR Service. This integration takes care of creating the connection and makes it easy for microservices to locate it. You can easily add connections from microservices and use them to send and receive information.
 
 ## Drawbacks of the API Gateway pattern
 

docs/architecture/distributed-cloud-native-apps-containers/api-gateways/gateway-patterns.md

@@ -65,8 +65,8 @@ This is where .NET Aspire comes in - it's a stack that helps you create manageab
 
 - Makes it clear which microservices and other components are part of your app. You can see them in the App Host project code, and in the dashboard that appears whenever you debug your app.
 - Implements observability for you using OpenTelemetry, so you can easily get data on the performance and behavior of all your microservices without requiring your development teams to build it.
-- Makes it easy to use common backing services, such as databases and service buses, by providing out-of-the-box components for each one.
-- Implements resiliency in these components to prevent and recover from failures, without requiring your development teams to build it.
+- Makes it easy to use common backing services, such as databases and service buses, by providing out-of-the-box integrations for each one.
+- Implements resiliency in these integrations to prevent and recover from failures, without requiring your development teams to build it.
 
 If you've already started building and deploying microservices apps, then .NET Aspire may not help you, because it's opinionated about how they should be built and that might not match your design. However, if you're new to microservices and cloud-native design, or if you're starting an app from scratch, it can help to make the project easier and reduce development time.
 

docs/architecture/distributed-cloud-native-apps-containers/architecting-distributed-cloud-native-applications/different-distributed-architectures.md

@@ -56,11 +56,11 @@ Azure Redis Cache is available across a number of predefined configurations and
 
 ## Using Redis caches with .NET Aspire
 
-.NET Aspire includes several built-in components that can help you cache data in Redis, whether that service is running in Azure, in a container, or elsewhere. The components come in three types:
+.NET Aspire includes several built-in integrations that can help you cache data in Redis, whether that service is running in Azure, in a container, or elsewhere. The integrations come in three types:
 
-- **Caching.** This component stores frequently accessed data in a single instance of Redis.
-- **Distributed Caching.** Use this component if your Redis cache may consist of multiple servers.
-- **Output Caching.** Use this component if you want to cache complete HTTP responses, such as a full web page or a response to an API call in HTML format.
+- **Caching.** This integration stores frequently accessed data in a single instance of Redis.
+- **Distributed Caching.** Use this integration if your Redis cache may consist of multiple servers.
+- **Output Caching.** Use this integration if you want to cache complete HTTP responses, such as a full web page or a response to an API call in HTML format.
 
 In the app host, you add the Redis hosting package. In this case, we'll add a distributed cache:
 
@@ -79,7 +79,7 @@ builder.AddProject<Projects.ExampleProject>()
        .WithReference(cache)
 ```
 
-In the microservice where you want to use the cache, start by installing the component:
+In the microservice where you want to use the cache, start by installing the integration:
 
 ```dotnetcli
 dotnet add package Aspire.StackExchange.Redis.DistributedCaching

docs/architecture/distributed-cloud-native-apps-containers/chpt8-data-patterns/azure-caching.md

@@ -193,7 +193,7 @@ To partition the container, items are divided into distinct subsets called logic
 
 One of the most important ways .NET Aspire helps cloud-native developers is by managing backing services and making it easy for microservices to discover them and communicate with them. Database services like Cosmos DB, SQL Server, or MongoDB are typical examples of backing services that support your microservices by persisting data.
 
-In .NET Aspire, there are built-in components, each of which supports a different backing service. The following database systems have .NET Aspire components, available out-of-the-box:
+In .NET Aspire, there are built-in integrations, each of which supports a different backing service. The following database systems have .NET Aspire integrations, available out-of-the-box:
 
 - Azure Cosmos DB
 - Azure Table Storage
@@ -203,7 +203,7 @@ In .NET Aspire, there are built-in components, each of which supports a differen
 - PostgreSQL
 - SQL Server
 
-Other database components are likely to become available from Microsoft or third parties. If you use one of these components, you still have to code operations like read, write, and delete, but you don't have to write code that manages the database clients and enables microservices to discover them.
+Other database integrations are likely to become available from Microsoft or third parties. If you use one of these integrations, you still have to code operations like read, write, and delete, but you don't have to write code that manages the database clients and enables microservices to discover them.
 
 ## NewSQL databases
 

docs/architecture/distributed-cloud-native-apps-containers/chpt8-data-patterns/relational-vs-nosql-data.md

@@ -166,7 +166,7 @@ Access to the key vault can be monitored to ensure that only the expected applic
 
 #### Azure Key Vault and .NET Aspire
 
-You don't have to use .NET Aspire to connect your cloud-native app to Azure Key Vault, but if you do, much of the work is done for you because .NET Aspire includes a built-in Key Vault component. You can create and configure a Key Vault backing service centrally, in the .NET Aspire app host project. Then, you pass that service to every microservice that uses keys.
+You don't have to use .NET Aspire to connect your cloud-native app to Azure Key Vault, but if you do, much of the work is done for you because .NET Aspire includes a built-in Key Vault integration. You can create and configure a Key Vault backing service centrally, in the .NET Aspire app host project. Then, you pass that service to every microservice that uses keys.
 
 In such a microservice, you use dependency injection to retrieve the backing service and then interact with it using a `SecretClient` object as normal. You can, for example, retrieve a password from the vault and use it to authenticate with another microservice.
 

docs/architecture/distributed-cloud-native-apps-containers/cloud-native-identity/azure-security.md

@@ -34,7 +34,7 @@ Beyond role-based authorization, Keycloak offers fine-grained authorization serv
 
 ## Keycloak and .NET Aspire
 
-The .NET Aspire stack includes a built-in component to help you interact with Keycloak. As with other .NET Aspire components, you create a Keycloak backing service in the .NET Aspire app host project, and then pass it to the microservices that authenticate users.
+The .NET Aspire stack includes a built-in integration to help you interact with Keycloak. As with other .NET Aspire integrations, you create a Keycloak backing service in the .NET Aspire app host project, and then pass it to the microservices that authenticate users.
 
 In each of those microservices, you can add authentication types and configure their options to identify users. For example, this code adds JSON Web Token (JWT) bearer authentication:
 

docs/architecture/distributed-cloud-native-apps-containers/cloud-native-identity/keycloak.md

@@ -148,11 +148,11 @@ Understanding the strengths and limitations of each communication pattern is cru
 
 If you choose to use the .NET Aspire stack to build your cloud-native app, synchronous communications must be implemented with HTTP, HTTPS, or gRPC calls. .NET Aspire is not involved in this communication.
 
-For asynchronous communications, .NET Aspire has components that help you work with queues in Azure Storage, RabbitMQ, Azure Service Bus, Apache Kafka, and NATS. You create these backing services in the app host project, and pass them to each microservice that uses them. In the microservices, you can use dependency injection to obtain objects that store and retrieve messages from queues in your preferred service.
+For asynchronous communications, .NET Aspire has integrations that help you work with queues in Azure Storage, RabbitMQ, Azure Service Bus, Apache Kafka, and NATS. You create these backing services in the app host project, and pass them to each microservice that uses them. In the microservices, you can use dependency injection to obtain objects that store and retrieve messages from queues in your preferred service.
 
-For streaming communications, use the .NET Aspire Apache Kafka component.
+For streaming communications, use the .NET Aspire Apache Kafka integration.
 
-Using .NET Aspire components also helps to improve resiliency. Some components can automatically retry requests that have failed, and you can configure timeouts for these retries.
+Using .NET Aspire integrations also helps to improve resiliency. Some integrations can automatically retry requests that have failed, and you can configure timeouts for these retries.
 
 In the next chapter we'll explore in more detail service-to-service communication patterns.
 

docs/architecture/distributed-cloud-native-apps-containers/communication-patterns/when-to-use-each-approach.md

@@ -28,9 +28,9 @@ Of course, you could always build your own service bus features on top of lower-
 
 Once you have decided that you want to have asynchronous and event-driven communication, you should choose the service bus product that best fits your needs for production.
 
-## Implementing the Azure Service Bus component with .NET Aspire
+## Implementing the Azure Service Bus integration with .NET Aspire
 
-.NET Aspire makes it much more straightforward to implement an event bus, because it includes built-in components for systems like:
+.NET Aspire makes it much more straightforward to implement an event bus, because it includes built-in integrations for systems like:
 
 - RabbitMQ
 - Azure Service Bus
@@ -54,7 +54,7 @@ The first step is to install the Azure Service Bus hosting package in the app ho
 dotnet add package Aspire.Hosting.Azure.ServiceBus
 ```
 
-Then, in the app host _Program.cs_ file, you can register the Service Bus component and consume the service as follows:
+Then, in the app host _Program.cs_ file, you can register the Service Bus integration and consume the service as follows:
 
 ```csharp
 var builder = DistributedApplication.CreateBuilder(args);
@@ -98,7 +98,7 @@ public class ExampleService
 
 ### Configuration
 
-The .NET Aspire Service Bus component offers several configuration options to tailor the `ServiceBusClient` to your project's needs. You can use configuration providers to load settings from `appsettings.json` or other configuration files using the `Aspire:Azure:Messaging:ServiceBus` key.
+The .NET Aspire Service Bus integration offers several configuration options to tailor the `ServiceBusClient` to your project's needs. You can use configuration providers to load settings from `appsettings.json` or other configuration files using the `Aspire:Azure:Messaging:ServiceBus` key.
 
 Here's an example of how you might configure the ServiceBusClient in your `appsettings.json`:
 
@@ -116,7 +116,7 @@ Here's an example of how you might configure the ServiceBusClient in your `appse
 }
 ```
 
-For more information, see [.NET Aspire Azure Service Bus component](https://learn.microsoft.com/dotnet/aspire/messaging/azure-service-bus-component?tabs=dotnet-cli)
+For more information, see [.NET Aspire Azure Service Bus integration](https://learn.microsoft.com/dotnet/aspire/messaging/azure-service-bus-integration?tabs=dotnet-cli)
 
 ## Integration events
 

docs/architecture/distributed-cloud-native-apps-containers/event-based-communication-patterns/integration-event-based-microservice-communications.md

@@ -149,7 +149,7 @@ builder.AddProject<Projects.ExampleProject>()
        .WithReference(messaging);
 ```
 
-For more information, see [.NET Aspire RabbitMQ component](https://learn.microsoft.com/dotnet/aspire/messaging/rabbitmq-client-component)
+For more information, see [.NET Aspire RabbitMQ integration](https://learn.microsoft.com/dotnet/aspire/messaging/rabbitmq-client-integration)
 
 ## Additional resources