6fce63d8dc
* Update Readme.md * Update Readme.md |
||
|---|---|---|
| .. | ||
| actor | ||
| architecture | ||
| bindings | ||
| components | ||
| extending-dapr | ||
| publish-subscribe-messaging | ||
| security | ||
| service-invocation | ||
| state-management | ||
| tracing-logging | ||
| README.md | ||
README.md
Dapr concepts
This directory contains various Dapr concepts. The goal of these documents is to expand your knowledge on the Dapr spec.
Core Concepts
-
A binding provides defines a bi-directional connection to an external cloud/on-premise service or system. Dapr allows you to invoke the external service through the standard Dapr binding API, and it allows your application to be triggered by events snet by the connected service.
-
Components
Dapr uses a modular design, in which functionalities are grouped and delivered by a number of components, such as pub-sub and secrets. Many of the components are pluggable so that you can swap out the default implemenation with your custom implementations.
-
Distirbuted tracing collects and aggregates trace events by transactions. It allows you to trace the entire call chain across multiple services. Dapr integrates with OpenTelemetry for distributed tracing and metrics collection.
-
Pub-sub is a loosely coupled messaging pattern where senders (or publishers) publishes messages to a topic, to which subscribers subscribe. Dapr natively supports the pub-sub pattern.
-
In Dapr, a secret is any piece of private information that you want to guard against unwanted users. Dapr offers a simple secret API and integrates with secret stores such as Azure Key Vault and Kubernetes secret stores to store the secrets.
-
Application state is anything an application wants to perserve beyound a single session. Dapr allows pluggable state stores behind a key/value-based state API.