Dapr in Practice

Stop writing vendor-specific code. Dapr's sidecar provides standard APIs for building portable microservices that can run on any cloud.

#1about 3 minutes

The challenges of building distributed applications

Distributed applications require managing platform concerns, cross-cutting issues, and application-level integrations, with Dapr addressing the latter two.

#2about 5 minutes

Decoupling applications with Dapr building blocks

Dapr replaces direct SDK integrations with standardized building blocks, like pub/sub, which are implemented by pluggable components for different cloud services.

#3about 3 minutes

How Dapr works using the sidecar pattern

Dapr runs as a sidecar container in Kubernetes, intercepting requests to provide features like service invocation and pub/sub without complex application code.

#4about 3 minutes

Achieving full application portability with Dapr

By abstracting infrastructure integrations, Dapr enables full application portability, allowing you to switch cloud services or databases without changing your code.

#5about 3 minutes

Handling use cases not covered by Dapr

For functionality not covered by Dapr building blocks, isolate the non-portable code in a separate microservice to maintain the core application's portability.

#6about 3 minutes

Provisioning resources with platform engineering tools

Platform teams can use tools like Crossplane to declaratively provision the underlying infrastructure resources that Dapr components rely on.

#7about 2 minutes

Summary and key considerations for adopting Dapr

Dapr is ideal when application portability is a strategic requirement and its building blocks cover the majority of your application's integration needs.

#8about 2 minutes

Q&A on Dapr workflows and distributed tracing

Dapr includes a built-in workflow engine similar to Temporal and supports distributed tracing across sync and async calls via OpenTelemetry context propagation.