5 Reasons Why You Should Use Microsoft Dapr to Build Event-driven Microservices

Why Dapr excels at building distributed, loosely-coupled, event-driven Microservices

Dunith Danushka
Tributary Data

--

A visual guide to Dapr by Nitya Narasimhan

Microservices architectures are inherently distributed. Building Microservices always bring in the most challenging problems, such as resilient service invocation, distributed transactions, on-demand scaling, and exactly-once processing of messages.

Putting Microservices on Kubernetes doesn’t always solve these problems as Kubernetes doesn’t have an application logic. Frameworks like Spring Boot, Akka, and Quarkus offered great help when building distributed Microservices architectures. But they are tightly coupled to specific programming languages and often opinionated.

So developers remain searching for a portable runtime to build distributed, scalable, and event-driven Microservices.

Dapr — Distributed Application Runtime

Dapr is a portable, event-driven runtime that makes it easy for any developer to build resilient, stateless, and stateful applications that run on the cloud and edge and embraces the diversity of languages and developer frameworks.

--

--

Dunith Danushka
Tributary Data

Editor of Tributary Data. Technologist, Writer, Senior Developer Advocate at Redpanda. Opinions are my own.