pull base content,head:MicrosoftDocs:main,into:wwlpublishsync

Author: wwlpublish

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/1-introduction.yml

@@ -5,7 +5,7 @@ metadata:
   description: Learn how to add fault tolerance to your cloud-native ASP.NET Core microservice app, with minimal impact on the user.
   author: codemillmatt
   ms.author: masoucou
-  ms.date: 11/06/2023
+  ms.date: 05/09/2025
   ms.topic: unit
 title: Introduction
 durationInMinutes: 1

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/2-application-infrastructure-resiliency.yml

@@ -5,7 +5,7 @@ metadata:
   description: Learn about approaches to resiliency for cloud-native microservices apps.
   author: codemillmatt
   ms.author: masoucou
-  ms.date: 11/06/2023
+  ms.date: 05/09/2025
   ms.topic: unit
 title: Application and infrastructure resiliency
 durationInMinutes: 5

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/3-implement-application-resiliency.yml

@@ -5,7 +5,7 @@ metadata:
   description: Learn how to use .NET resiliency with cloud-native microservices apps.
   author: codemillmatt
   ms.author: masoucou
-  ms.date: 11/06/2023
+  ms.date: 05/09/2025
   ms.topic: unit
   ms.custom: devx-track-dotnet
 title: Implement application resiliency

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/4-exercise-implement-resiliency.yml

@@ -5,7 +5,7 @@ metadata:
   description: Write code to add resiliency to an existing cloud-native microservices app.
   author: codemillmatt
   ms.author: masoucou
-  ms.date: 11/06/2023
+  ms.date: 05/09/2025
   ms.topic: unit
 title: Exercise - Implement application resiliency
 durationInMinutes: 9

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/5-implement-infrastructure-resiliency.yml

@@ -5,7 +5,7 @@ metadata:
   description: Learn how to use Linkerd to configure infrastructure-based resiliency in your microservices app.
   author: codemillmatt
   ms.author: masoucou
-  ms.date: 11/06/2023
+  ms.date: 05/09/2025
   ms.topic: unit
   ms.custom:
     - devx-track-dotnet

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/6-exercise-implement-infrastructure-resiliency.yml

@@ -5,7 +5,7 @@ metadata:
   description: Use Linkerd to configure infrastructure-based resiliency in your microservices app.
   author: codemillmatt
   ms.author: masoucou
-  ms.date: 11/06/2023
+  ms.date: 05/09/2025
   ms.topic: unit
 title: Exercise - Implement infrastructure resiliency with Kubernetes
 durationInMinutes: 11

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/7-knowledge-check.yml

@@ -5,7 +5,7 @@ metadata:
   description: Test your knowledge of what you learned in this tutorial about resiliency.
   author: codemillmatt
   ms.author: masoucou
-  ms.date: 11/06/2023
+  ms.date: 05/09/2025
   ms.topic: unit
 title: Module assessment
 durationInMinutes: 7

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/8-summary.yml

@@ -5,7 +5,7 @@ metadata:
   description: Review what you learned in the tutorial, and deprovision the Azure resources that you used.
   author: codemillmatt
   ms.author: masoucou
-  ms.date: 11/06/2023
+  ms.date: 05/09/2025
   ms.topic: unit
   ms.custom:
     - devx-track-dotnet

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/includes/1-introduction.md

@@ -13,7 +13,7 @@ You'll modify the app to include some code-based resiliency handling policies in
 
 ## Learning objectives
 
-In this module, you will:
+In this module, you'll:
 
 * Understand foundational resiliency concepts.
 * Observe the behavior of a microservice that has no resiliency strategy.
@@ -25,4 +25,4 @@ In this module, you will:
 * Familiarity with C# and .NET development at the beginner level.
 * Familiarity with RESTful service concepts.
 * Conceptual knowledge of containers and AKS at the intermediate level.
-* Ability to run development containers GitHub Codespaces or in Visual Studio Code.
+* Ability to run development containers GitHub Codespaces or in Visual Studio Code.

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/includes/2-application-infrastructure-resiliency.md

@@ -6,7 +6,7 @@ Because microservice environments can be volatile, design your apps to expect an
 
 In designing resilient applications, you often have to choose between failing fast and graceful degradation. Failing fast means the application will immediately throw an error or exception when something goes wrong, rather than try to recover or work around the problem. This allows issues to be identified and fixed quickly. Graceful degradation means the application will try to keep operating in a limited capacity even when some component fails.
 
-In cloud-native applications it's important for services to handle failures gracefully rather than fail fast. Since microservices are decentralized and independently deployable, partial failures are expected. Failing fast would allow a failure in one service to quickly take down dependent services, which reduce overall system resiliency. Instead, microservices should be coded to anticipate and tolerate both internal and external service failures. This graceful degradation allows the overall system to continue operating even if some services are disrupted. Critical user-facing functions can be sustained, avoiding a complete outage. Graceful failure also allows disturbed services time to recover or self-heal before impacting the rest of the system. So for microservices-based applications, graceful degradation better aligns with resiliency best practices like fault isolation and rapid recovery. It prevents local incidents from cascading across the system.
+In cloud-native applications, it's important for services to handle failures gracefully rather than fail fast. Since microservices are decentralized and independently deployable, partial failures are expected. Failing fast would allow a failure in one service to quickly take down dependent services, which reduce overall system resiliency. Instead, microservices should be coded to anticipate and tolerate both internal and external service failures. This graceful degradation allows the overall system to continue operating even if some services are disrupted. Critical user-facing functions can be sustained, avoiding a complete outage. Graceful failure also allows disturbed services time to recover or self-heal before impacting the rest of the system. So for microservices-based applications, graceful degradation better aligns with resiliency best practices like fault isolation and rapid recovery. It prevents local incidents from cascading across the system.
 
 There are two fundamental approaches to support a graceful degradation with resiliency: application and infrastructure. Each approach has benefits and drawbacks. Both approaches can be appropriate depending on the situation. This module explains how to implement both *code-based* and *infrastructure-based* resiliency.
 
@@ -28,11 +28,11 @@ A *Circuit Breaker* strategy gives a target service a break after a repeated num
 
 ### Infrastructure-based resiliency
 
-To implement infrastructure-based resiliency, you can use a *service mesh*. Aside from resiliency without changing code, a service mesh provides traffic management, policy, security, strong identity, and observability. Your app is decoupled from these operational capabilities, which are moved to the infrastructure layer. 
+To implement infrastructure-based resiliency, you can use a *service mesh*. Aside from resiliency without changing code, a service mesh provides traffic management, policy, security, strong identity, and observability. Your app is decoupled from these operational capabilities, which are moved to the infrastructure layer.
 
 #### Comparison to code-based approaches
 
-An infrastructure-based resiliency approach can use a metrics-based view that allows it to adapt dynamically to cluster conditions in real time. This approach adds another dimension to managing the cluster, but doesn't add any code.
+An infrastructure-based resiliency approach can use a metrics-based view that allows it to adapt dynamically to cluster conditions in real time. This approach adds another dimension to managing the cluster but doesn't add any code.
 
 With a code-based approach you:
 
@@ -43,4 +43,4 @@ There's no reasonable way to respond to an infrastructure failure in your app's
 
 In contrast, infrastructure-based approaches are unaware of app internals. For example, complex database transactions are invisible to service meshes. Such transactions can only be protected from failure with a code based approach.
 
-In upcoming units, you'll implement resilience for a microservice based app  using .NET HTTP resiliency in code and a Linkerd service mesh.
+In upcoming units, you'll implement resilience for a microservice based app using .NET HTTP resiliency in code and a Linkerd service mesh.