Pluggable components overview

Mon, 01 Jan 0001 00:00:00 +0000

Pluggable components are components that are not included as part the runtime, as opposed to the built-in components included with dapr init. You can configure Dapr to use pluggable components that leverage the building block APIs, but are registered differently from the built-in Dapr components.

Pluggable components vs. built-in components

Dapr provides two approaches for registering and creating components:

The built-in components included in the runtime and found in the components-contrib repository .
Pluggable components which are deployed and registered independently.

While both registration options leverage Dapr’s building block APIs, each has a different implementation processes.

How to: Implement pluggable components

Mon, 01 Jan 0001 00:00:00 +0000

In this guide, you’ll learn why and how to implement a pluggable component. To learn how to configure and register a pluggable component, refer to How to: Register a pluggable component

Implement a pluggable component

In order to implement a pluggable component, you need to implement a gRPC service in the component. Implementing the gRPC service requires three steps:

Find the proto definition file

Proto definitions are provided for each supported service interface (state store, pub/sub, bindings, secret stores).

Pluggable components on Dapr Docs

Pluggable components overview

Pluggable components vs. built-in components

How to: Implement pluggable components

Implement a pluggable component

Find the proto definition file