Components

Dapr uses a modular design where functionality is delivered as a component. Each component has an interface definition. All of the components are pluggable so that you can swap out one component with the same interface for another. The components contrib repo is where you can contribute implementations for the component interfaces and extends Dapr’s capabilities.

A building block can use any combination of components. For example the building block and the state management building block both use . As another example, the Pub/Sub building block uses .

The following are the component types provided by Dapr:

• Bindings
• Service discovery name resolution
• Tracing exporters

Service discovery components are used with the building block to integrate with the hosting environment to provide service-to-service discovery. For example, the Kubernetes service discovery component integrates with the Kubernetes DNS service and self hosted uses mDNS.

In Dapr, a secret is any piece of private information that you want to guard against unwanted users. Secrets stores, used to store secrets, are Dapr components and can be used by any of the building blocks.