Overview of Dapr in self-hosted mode

Dapr can be configured to run in self-hosted mode on your local developer machine or on production VMs. 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.

Dapr can be initialized with Docker (default) or in . It can also be initialized and run in offline or airgap environments. The default Docker setup provides out of the box functionality with the following containers and configuration:

• A Redis container configured to serve as the default component for both state management and publish/subscribe.
• A default Dapr configuration and components installed in (Mac/Linux) or (Windows).

You can use the to a Dapr sidecar process along with your application. Additional arguments and flags can be found here.

If you are running Dapr on virtual machines or where mDNS is not available, then you can use the component for name resolution.