Skip to content

Latest commit

 

History

History
42 lines (22 loc) · 2.34 KB

README.md

File metadata and controls

42 lines (22 loc) · 2.34 KB

Dapr concepts

This directory contains various Dapr concepts. The goal of these documents is to expand your knowledge on the Dapr spec.

Core Concepts

  • Bindings

    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 sent by the connected service.

  • Building blocks

    A building block is a single-purposed API surface backed by one or more Dapr components. Dapr consists of a set of building blocks, with extensibility to add new building blocks.

  • 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.

  • Distributed Tracing

    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

    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.

  • Secrets

    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.

  • State

    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.

Actors

Extensibility