An event-driven, portable runtime for building microservices on cloud and edge.
github.com/dapr (GoLang, MIT license)
"Dapr injects a side-car container/process to each compute unit.
The side-car interacts with event triggers and communicates with the compute unit via standard HTTP or gRPC protocols. This enables Dapr to support all existing and future programming languages without requiring you to import frameworks or libraries.
Dapr offers built-in state management, reliable messaging (at least once delivery), triggers and bindings through standard HTTP verbs or gRPC interfaces. This allows you to write stateless, stateful and actor-like services following the same programming paradigm. You can freely choose consistency model, threading model and message delivery patterns.
Dapr runs natively on Kubernetes, as a standalone binary on your machine, on an IoT device, or as a container that can be injected into any system, in the cloud or on-premises.
Dapr uses pluggable state stores and message buses such as Redis as well as gRPC to offer a wide range of communication methods, including direct dapr-to-dapr using gRPC and async Pub-Sub with guaranteed delivery and at-least-once semantics."
"Dapr is a distributed application runtime. Unlike a service mesh which is focused on networking concerns, Dapr is focused on providing building blocks that make it easier for developers to build microservices. Dapr is developer-centric versus service meshes being infrastructure-centric."
Learn all about Distributed Application Runtime (Dapr), Part 1 | Azure Friday @YouTube (Channel 9)
Dapr, Rudr, OAM | Mark Russinovich presents next gen app development & deployment (Microsoft Ignite)
A sidecar is a one-wheeled device attached to the side of a motorcycle, scooter, or bicycle, making the whole a three-wheeled vehicle. A motorcycle with a sidecar is sometimes called a combination, an outfit, a rig or a hack
Sidecar on Vespa scooter
"In software architecture, a service mesh is a dedicated infrastructure layer for facilitating service-to-service communications between microservices, often using a sidecar proxy.
Having such a dedicated communication layer can provide a number of benefits, such as providing observability into communications, providing secure connections, or automating retries and backoff for failed requests."