Dapr and the problem it solves

Dapr addresses a large challenge inherent in modern distributed applications:?Complexity.

Through an architecture of pluggable components, Dapr greatly simplifies the plumbing behind distributed applications. It provides a?dynamic glue?that binds your application with infrastructure capabilities from the Dapr runtime.

Consider a requirement to make one of your services stateful. What would be your design? You could write custom code that targets a state store such as Redis Cache. However, Dapr provides state management capabilities out of the box. Your service invokes the Dapr state management?building block?that dynamically binds to a state store?component?via a Dapr?component configuration?yaml file. Dapr ships with several pre-built state store components, including Redis. With this model, your service delegates state management to the Dapr runtime. Your service has no SDK, library, or direct reference to the underlying component. You can even change state stores, say, from Redis to MySQL or Cassandra, with no code changes.