Dapr terminology and definitions
Definitions for common terms and acronyms in the Dapr documentation
This page details all of the common terms you may come across in the Dapr docs.
|A running service/binary, usually one that you as the user create and run.
|An API that Dapr provides to users to help in the creation of microservices and applications.
|Dapr building blocks
|Modular types of functionality that are used either individually or with a collection of other components, by a Dapr building block.
|A YAML file declaring all of the settings for Dapr sidecars or the Dapr control plane. This is where you can configure control plane mTLS settings, or the tracing and middleware settings for an application instance.
|Distributed Application Runtime.
|Dapr control plane
|A collection of services that are part of a Dapr installation on a hosting platform such as a Kubernetes cluster. This allows Dapr-enabled applications to run on the platform and handles Dapr capabilities such as actor placement, Dapr sidecar injection, or certificate issuance/rollover.
|HTTPEndpoint is a Dapr resource use to identify non-Dapr endpoints to invoke via the service invocation API.
|Service invocation API
|Windows/macOS/Linux machine(s) where you can run your applications with Dapr. Dapr provides the capability to run on machines in “self-hosted” mode.
|A running application or binary. This can refer to your application or to a Dapr application.
|A program that runs alongside your application as a separate process or container.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified May 18, 2023: Extend service invocation to non-Dapr endpoints docs (#3384) (c1f152a9)