Skip to content

Commit e177d2a

Browse files
committed
start section
Signed-off-by: Hannah Hunter <[email protected]>
1 parent b03b2dc commit e177d2a

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/container-apps/dapr-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,10 @@ Configure microservices APIs for your container apps environment with a [Dapr-en
2525
| 2 | Dapr | The fully managed Dapr APIs are exposed to each container app through a Dapr sidecar. The Dapr APIs can be invoked from your container app via HTTP or gRPC. The Dapr sidecar runs on HTTP port 3500 and gRPC port 50001. |
2626
| 3 | Dapr component configuration | Dapr uses a modular design where functionality is delivered as a component. Dapr components can be shared across multiple container apps. The Dapr app identifiers provided in the scopes array dictate which dapr-enabled container apps load a given component at runtime. |
2727

28+
## Dapr in Azure Container Apps vs. Dapr open source
29+
30+
31+
2832
## Versioning
2933

3034
Instead of following a fixed release schedule, Dapr in Azure Container Apps releases new features and functionality based on the prioritization and stability of the Dapr binaries. [Learn more about Dapr releases in Azure Container Apps.](./faq.yml#how-often-are-dapr-versions-released-for-azure-container-apps-)

0 commit comments

Comments
 (0)