The documentation you are viewing is for Dapr v1.0 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Overview of Dapr in self-hosted mode
Dapr can be configured to run on your local developer machine in self hosted mode. Each running service has a Dapr runtime process (or sidecar) which is configured to use state stores, pub/sub, binding components and the other building blocks.
In self hosted mode, Redis is running locally in a container and is configured to serve as both the default component for state store and for pub/sub. A Zipkin container is also configured for diagnostics and tracing. After running
dapr init, see the
$HOME/.dapr/components directory (Mac/Linux) or
%USERPROFILE%\.dapr\components on Windows.
dapr-placement service is responsible for managing the actor distribution scheme and key range settings. This service is only required if you are using Dapr actors. For more information on the actor
Placement service read actor overview.
You can use the Dapr CLI to run a Dapr enabled application on your local machine.