This is the core Dapr repository, a CNCF-graduated distributed application runtime. In production it operates as a sidecar (daprd) alongside application containers, exposing HTTP and gRPC building-block APIs for state management, pub/sub messaging, service invocation, actors, durable workflows, secrets, configuration, distributed locks, jobs, and cryptography. The repo also contains the control-plane services: operator for Kubernetes resource management, injector for sidecar injection, placement for actor distribution, scheduler for distributed job/reminder coordination, and sentry for mTLS certificate issuance. The codebase is written primarily in Go with protobuf service definitions, Helm charts, and a large integration test harness that runs real system binaries. Architecturally, the runtime is modular: a component registry pattern supports pluggable state stores, pub/sub brokers, bindings, secret stores, and middleware; a runtime processor handles component lifecycle with hot-reload; the actor subsystem includes placement protocols, consistent hashing, reminders, timers, and workflow targets; and the workflow engine is built on durabletask-go with state signing, reruns, child workflows, and pending-start redrive. The integration test suite is extensive and treats process orchestration as a first-class concern, with dozens of suites for workflows, actors, scheduler, placement, subscriptions, state, and security. The engineering quality is strong: interface-driven abstractions, extensive fakes, versioned component APIs, resilient retry/backoff utilities, circuit breakers, and observability are all present. Occasional drift appears in deprecated OpenCensus metric usage, legacy version-skew patches, and a large build-tag matrix, but the project is actively maintained with recent commits, automated CI, and regular releases. This is a production infrastructure platform, not a data/research codebase.

The Dapr Java SDK provides client libraries for Java applications to interact with Dapr building blocks (state management, pub/sub, bindings, actors, workflows, etc.). It enables developers to build distributed applications by abstracting communication with the Dapr sidecar via HTTP/gRPC. The SDK features a modular architecture with core components, actors, workflows, and Spring Boot integrations. Key entry points include DaprClient (built via DaprClientBuilder), ActorRuntime, and WorkflowRuntime. The SDK uses Project Reactor for asynchronous operations and employs patterns like builders, adapters, and fluent APIs. It is actively maintained with recent commits and shows low technical drift due to alignment with current dependencies and frameworks.

Dapr Dashboard is a web-based UI for Dapr (Distributed Application Runtime) that provides visibility into Dapr applications, components, and configurations. The application consists of a Go backend serving REST APIs and WebSocket connections, and an Angular frontend. It supports three deployment platforms: Kubernetes, Standalone (self-hosted), and Docker Compose. The backend uses platform-specific adapters to interact with each environment, querying Kubernetes APIs, local filesystems, or Docker Compose configurations as needed. The frontend displays instance information, component details, configuration data, control plane status (Kubernetes-only), and real-time log streaming via WebSocket. Despite recent commits, the project is explicitly marked as archived in the README, with users directed to Diagrid Dashboard as an alternative.