dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update daprdocs/content/en/operations/dapr-shared/dapr-shared.md 

Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
This commit is contained in:
salaboy 2024-05-02 14:52:05 +01:00
parent 4025856528
commit 6f142b3fc0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/operations/dapr-shared/dapr-shared.md
View File

@ -28,7 +28,7 @@ By default, when Dapr is installed into a Kubernetes Cluster, the Dapr Control P
<img src="/images/dapr-shared/sidecar.png" width=800 style="padding-bottom:15px;">
While sidecars are the default strategy, there are some use cases that require other approaches. For example, you want to decouple the lifecycle of your workloads from the Dapr APIs. A typical example of this is Functions, or function as a service runtimes, which might automatically downscale your idle workloads to free up resources. For such cases, keeping the Dapr APIs and all the Dapr async functionalities (such as subscriptions) might be required. Dapr Shared was created exactly for this kind of scenario.
While sidecars are Dapr's default deployment strategy, some use cases require other approaches. Let's say you want to decouple the lifecycle of your workloads from the Dapr APIs. A typical example of this is functions, or function-as-a-service runtimes, which might automatically downscale your idle workloads to free up resources. For such cases, keeping the Dapr APIs and all the Dapr async functionalities (such as subscriptions) separate might be required.
Dapr Shared extends the Dapr sidecar model with two new deployment strategies: DaemonSet and Deployment.