Skip to content

Commit 50dc1a2

Browse files
Verified the article, reviewed the content, and fixed all editorial issues. Updated ms.date w.r.t freshness pass.
1 parent 385966d commit 50dc1a2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/container-apps/microservices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: container-apps
55
author: craigshoemaker
66
ms.service: azure-container-apps
77
ms.topic: conceptual
8-
ms.date: 08/02/2024
8+
ms.date: 04/01/2025
99
ms.author: cshoe
1010
ms.custom: build-2023
1111
---
@@ -26,7 +26,7 @@ You can add [**Azure Functions**](https://aka.ms/functionsonaca) and [**Azure Sp
2626

2727
## Dapr integration
2828

29-
When implementing a system composed of microservices, function calls are spread across the network. To support the distributed nature of microservices, you need to account for failures, retries, and timeouts. While Container Apps features the building blocks for running microservices, use of [Dapr](https://docs.dapr.io/concepts/overview/) provides an even richer microservices programming model. Dapr includes features like observability, pub/sub, and service-to-service invocation with mutual TLS, retries, and more.
29+
When you implement a system with microservices, function calls are distributed across the network. To support the distributed nature of microservices, you need to account for failures, retries, and time-outs. While Azure Container Apps features the building blocks for running microservices, integrating [Dapr](https://docs.dapr.io/concepts/overview/) enhances the microservices programming model. Dapr offers more features such as observability, pub/sub, and service-to-service invocation with mutual TLS, retries, and more.
3030

3131
For more information on using Dapr, see [Build microservices with Dapr](microservices-dapr.md).
3232

0 commit comments

Comments
 (0)