sidecar架构
Sidecar architecture
- Dapr将其api公开为一个sidecar架构，可以是容器，也可以是进程，不需要应用程序代码包含任何Dapr运行时代码。这使得与Dapr的集成与其他运行时更加容易，并且提供了应用程序逻辑的分离，以提高可支持性。
Dapr exposes its APIs as a sidecar architecture, either as a container or as a process, not requiring the application code to include any Dapr runtime code. This makes integration with Dapr easy from other runtimes, as well as providing separation of the application logic for improved supportability.
托管环境
Hosting Environments
- Dapr可以托管在多个环境中，包括用于本地开发的自托管或部署到vm、Kubernetes和边缘环境（如azureiot edge）的集群。
Dapr can be hosted in multiple environments, including self hosted for local development or to deploy to a group of VMs, Kubernetes and edge environments such as Azure IoT Edge.
Self hosted 自托管
- 在自托管模式下，Dapr作为一个单独的side car进程运行，您的服务代码可以通过HTTP或gRPC调用它。在自托管模式下，您还可以将Dapr部署到一组vm上。
In self hosted mode Dapr runs as a separate side-car process which your service code can call via HTTP or gRPC. In self hosted mode, you can also deploy Dapr onto a set of VMs.
自托管.png
Kubernetes hosted k8s托管
- 在Kubernetes等容器托管环境中，Dapr作为一个边车容器运行，应用程序容器位于同一个pod中。
In container hosting environments such as Kubernetes, Dapr runs as a side-car container with the application container in the same pod.
