{"id":80049,"date":"2020-04-29T09:00:35","date_gmt":"2020-04-29T16:00:35","guid":{"rendered":""},"modified":"2023-12-29T14:24:38","modified_gmt":"2023-12-29T22:24:38","slug":"distributed-application-runtime-dapr-growth-community-update","status":"publish","type":"post","link":"https:\/\/opensource.microsoft.com\/blog\/2020\/04\/29\/distributed-application-runtime-dapr-growth-community-update\/","title":{"rendered":"How Distributed Application Runtime (Dapr) has grown since its announcement"},"content":{"rendered":"\n

Since the October 2019 announcement<\/a> of the Distributed Application Runtime (Dapr<\/a>), we have seen a tremendous response and the emergence of an engaged Dapr community. Over the past six months, more than 120 contributors have jumped on board and participated in the effort to build and extend Dapr through the GitHub repos<\/a> \u2013 opening issues, offering feature proposals, taking part in discussions, and making more than 350 distinct code contributions. This community engagement has demonstrated that Dapr enables developers from all backgrounds to solve some of the toughest challenges when developing distributed applications. We are grateful for the engagement and participation from the community helping us make Dapr better.<\/p>\n\n\n\n

On top of the community response, we have also been busy working with customers around the world and from different industries to use Dapr for developing business-critical workloads. These customer engagements have been a tremendous source of feedback and participation, helping shape the roadmap for Dapr and putting Dapr on a path towards a stable v1.0 release. In future blog posts, we\u2019ll share some of these real-world scenarios where Dapr is helping companies build their future applications.<\/p>\n\n\n\n

What is Dapr?<\/h2>\n\n\n\n

Dapr is an event-driven, portable runtime for building microservices on cloud and edge and embraces the diversity of languages and developer frameworks. Dapr codifies best practices for building distributed applications and at its core are API abstractions that provide common capabilities needed to build microservices, including state management, service invocation, pub\/sub messaging, secrets management, and others.<\/p>\n\n\n\n

Each capability is abstracted through a \u201cBuilding Block\u201d that defines a simple and consistent API decoupled from the technology chosen to implement it through the use of pluggable components. This best practice of decoupling frees developers from the burden of integrating and having a deep understanding of the underlying technologies they use. The use of building blocks also allows swapping implementations when the application is deployed in different hosting environments or when needs change as the application evolves without affecting your code. Developers are free to use all, a few, or even just one building block as needed.<\/p>\n\n\n\n

\"a<\/figure>\n\n\n\n

Since Dapr itself provides both HTTP REST or gRPC APIs, applications using Dapr are portable and can be written in any language. Furthermore, Dapr runs as a sidecar to the application so a developer using Dapr simply sends a call to the Dapr sidecar and Dapr takes care of the rest. Since Dapr is a process or container that runs alongside the application it can run in any environment including a local dev machine (running Linux, Mac, or Windows), a Kubernetes cluster, an ARM edge device, or any other compute infrastructure. Dapr is also not limited to either on-premises or cloud environments \u2013 it can run alongside any application, written in any language, deployed to any environment.<\/p>\n\n\n\n