dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

updates to overview.md and adding readme.md for reference docs (#104) 

* updates to overview and adding readme.md for reference docs

* updates to overview and adding readme.md for reference docs

* Changed Cosmos to CosmosDB

* Update readme.md
This commit is contained in:
Mark Fussell 2019-10-10 19:40:32 -07:00 committed by Yaron Schneider
parent 1a5de8e723
commit 13e7e667b1
4 changed files with 30 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
images/overview.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 67 KiB

After

Width:  |  Height:  |  Size: 73 KiB

27
overview.md
View File

@ -1,39 +1,38 @@
# Dapr overview
Dapr is a portable, event-driven runtime that makes it easy for enterprise developers to build resilient, microservice stateless and stateful applications that run on the cloud and edge and embraces the diversity of languages and developer frameworks.
Dapr is a portable, event-driven runtime that makes it easy for enterprise developers to build resilient, microservice stateless and stateful applications that run on the cloud and edge and embraces the diversity of languages and developer frameworks.
## Any language, any framework, anywhere
Today we are experiencing a wave of cloud adoption. Developers are comfortable with web + database application architectures (for example classic 3-tier designs), but not with microservice application architectures which are inherently distributed. It’s hard to become a distributed systems expert, nor should you have to. Developers want to focus on business logic, while leaning on the platforms to imbue their applications with scale, resiliency, maintainability, elasticity and the other attributes of cloud-native architectures.
Today we are experiencing a wave of cloud adoption. Developers are comfortable with web + database application architectures (for example classic 3-tier designs) but not with microservice application architectures which are inherently distributed. It’s hard to become a distributed systems expert, nor should you have to. Developers want to focus on business logic, while leaning on the platforms to imbue their applications with scale, resiliency, maintainability, elasticity and the other attributes of cloud-native architectures.
This is where Dapr comes in. 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 completely independent and you can use one, some, or all of them in your application.
This is where Dapr comes in. 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 completely independent and you can use one, some, or all of them in your application.
In addition Dapr is platform agnostic meaning you can run your applications locally, on any Kubernetes cluster, and other hosting environments that Dapr integrates with. This enables you to build microservice applications that can run on both the cloud and edge.
In addition Dapr is platform agnostic meaning you can run your applications locally, on any Kubernetes cluster, and other hosting environments that Dapr integrates with. This enables you to build microservice applications that can run on the cloud and edge.
In summary, you can use Dapr to build microservice applications using any language, any framework, and run them anywhere.
Using Dapr you can easily build microservice applications using any language, any framework, and run them anywhere.
## What capabilities does Dapr provide?
There are many considerations when architecting and building microservices applications. Dapr provides best practices for common capabilities when building microservice applications that developers can use in a standard way and deploy to any environment. It does this by providing distributed system building blocks.
There are many considerations when architecting microservices applications. Dapr provides best practices for common capabilities when building microservice applications that developers can use in a standard way and deploy to any environment. It does this by providing distributed system building blocks.
Each of these building blocks is independent, meaning that you can use one, some or all of them in your application. In this first release of Dapr, the following building blocks are provided;
Each of these building blocks is independent, meaning that you can use one, some or all of them in your application. In this initial release of Dapr, the following building blocks are provided;
• **Service invocation** Resilent service-to-service invocaton enables method calls, including retries, on remote services wherever they are located in the supported hosting environment.
• **Service invocation** Resilient service-to-service invocation enables method calls, including retries, on remote services wherever they are located in the supported hosting environment.
• **State Management** With state management for key/value pairs, long running, highly available, stateful services as well as shorter lived, stateless services can be written easily in the same application. The state store is pluggable and can include Azure Cosmos, AWS DynamoDB or Redis among others.
• **State Management** With state management for storing key/value pairs, long running, highly available, stateful services can be easily written alongside stateless services in your application. The state store is pluggable and can include Azure CosmosDB, AWS DynamoDB or Redis among others.
• **Publish and subscribe messaging between services** Publishing events and subscribing to topics between services enables event-driven architectures to simplify horizontal scalability and make them resilient to failure. Dapr provides at least once message delivery guarantee.
• **Event driven resource bindings**. Resource bindings and triggers further builds on event-driven architectures for scale and resiliency by receiving and sending events to and from any external resource such as databases, queues, file systems, etc.
• **Event driven resource bindings** Resource bindings with triggers builds further on event-driven architectures for scale and resiliency by receiving and sending events to and from any external resource such as databases, queues, file systems, etc.
• **Actors** as the pattern for stateless and stateful objects that make concurrency simple with method and state encapsulation. Dapr provides many capabilities in its actor runtime including concurrency, state, life-cycle management for actor activation/deactivation and timers and reminders to wake up actors. Dapr also includes language specific actor SDKs built on this runtime for improved usability. And because these SDK share a common actor runtime, you even get cross-language actor support.
• **Actors** A pattern for stateless and stateful objects that make concurrency simple with method and state encapsulation. Dapr provides many capabilities in its actor runtime including concurrency, state, life-cycle management for actor activation/deactivation and timers and reminders to wake-up actors. Dapr also includes language specific actor SDKs built on this runtime for usability. Since these SDKs share a common actor runtime, you even get cross-language actor support.
•**Distributed tracing between services** to easily diagnose and observe inter-service calls in production using the W3C Trace Context standard.
•**Distributed tracing between services** To easily diagnose and observe inter-service calls in production using the W3C Trace Context standard.
## Dapr distributed system building blocks
The diagram below shows the distributed system building blocks provides by Dapr, exposed with standard APIs. These APIs can be used from any developer code over http or gRPC. Dapr integrates with any hosting platform to enable application portability including across cloud and edge.
The diagram below shows the distributed system building blocks provides by Dapr, exposed with standard APIs. These APIs can be used from any developer code over http or gRPC. Dapr integrates with any hosting platform, for example Kubernetes, to enable application portability including across cloud and edge.
![Dapr overview](images/overview.png)

18
readme.md
View File

@ -1,11 +1,13 @@
# Dapr documentation
Welcome to the documentation repository for Dapr. You can learn about Dapr from the below links.
Welcome to the Dapr documentation repository. You can learn more about Dapr from the below links.
- **[Overview](./overview.md)** - An overview of Dapr and how it enables you to build distributed applications
- **[Getting Started](./getting-started)** - Set up your environment with Dapr
- **[Quickstarts and Samples](./quickstart)** - Quick start guides and samples for developing apps using Dapr
- **[Concepts](./concepts)** - Core Dapr concepts explained
- **[How-Tos](./howto)** - Guides explaining how to accomplish specific tasks with Dapr
- **[Reference](./reference)** - Detailed reference documentation
- **[Getting Started with Actors](https://github.com/dapr/dotnet-sdk/blob/master/docs/get-started-dapr-actor.md)** - End to end tutorial for developing Actors applications using Dapr dotnet sdk
- **[Overview](./overview.md)** - An overview of Dapr and how it enables you to build distributed applications
- **[Getting Started](./getting-started)** - Set up your environment with Dapr
- **[Quickstarts and Samples](./quickstart)** - Quick start guides and samples for developing apps using Dapr
- **[Concepts](./concepts)** - Core Dapr concepts explained
- **[How-Tos](./howto)** - Guides explaining how to accomplish specific tasks with Dapr
- **[Reference](./reference)** - Detailed reference documentation
### SDKs
- **[Getting Started with .NET Actors](https://github.com/dapr/dotnet-sdk/blob/master/docs/get-started-dapr-actor.md)** - End to end tutorial for developing actor applications using the Dapr dotnet sdk

7
reference/readme.md Normal file
View File

@ -0,0 +1,7 @@
# Reference documentation
- **[Dapr CLI documentation](https://github.com/dapr/cli)**
- **[Dapr Specification](https://github.com/dapr/spec)**