What is Dapr?
Distributed APplication Runtime. An event-driven, portable runtime for building microservices on cloud and edge.
Why should you use Dapr?
Are you writing distributed applications?
Are you looking to build resilient, microservice applications and building your own internal mini-frameworks to make this happen?
Do you have your services written in multiple programming languages or frameworks?
Do you find it difficult to implement state handling, pub/sub messaging, which enable event-driven, resilient architectures?
Dapr enables developers using any language or framework to easily write microservices, providing industry best practices to solve distributed systems problems.
Checkout the git repo. If it fits your need then do not reinvent the wheel.
dapr / dapr
Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
Dapr is a portable, serverless, event-driven runtime that makes it easy for developers to build resilient, stateless and stateful microservices that run on the cloud and edge and embraces the diversity of languages and developer frameworks.
Dapr codifies the best practices for building microservice applications into open, independent, building blocks that enable you to build portable applications with the language and framework of your choice. Each building block is independent and you can use one, some, or all of them in your application.
Note: Dapr is currently under community development in alpha phase. Dapr is not recommended for production workloads until the 1.0 stable release.
- Enable developers using any language or framework to write distributed applications
- Solve the hard problems developers face building microservice applications by providing best practice building blocks
- Be community driven, open and vendor neutral
- Gain new contributors
- Provide consistency and…
Top comments (1)
You can learn more about #dapr on this Azure Friday session - channel9.msdn.com/Shows/Azure-Frid...