Introduction to DAPR: runtime for building distributed applications

At the moment, there are no doubts that transformation to the new architectural pattern, microservices architecture, is happening. Today, I want to emphasize that microservices architecture does not solve everything. This transformation is happening and my role here is to show you some possible ways how to minimize the struggle.

Transcript

1. Introduction to DAPR: runtime for building distributed applications Stepan Vrany Cloud Architect Twitter: @MstrsObserver LinkedIN: linkedin.com/in/stepanvrany 1
2. more and more companies build scalable, cloud native applications, they are using more and more managed services from Public Cloud providers and microservice architecture is becoming the new standard for building cloud native applications. Transformation is really happening 2
3. Microservice architecture brings to the game very interesting stuff: scalability, loose service coupling, and independent deployments. But it comes with a price: you need a lot of skills. Microservices can be hard 3
4. What if we have some platform to handle some difficult parts? 4
5. testing the layout 5 Enter the DAPR
6. testing the layout 6 DAPR Distributed Application Runtime
7. testing the layout 7 It comes from Microsoft, same as other pieces of amazing software for the Kubernetes ecosystem
8. It aims to provide some unified runtime for microservices by abstraction. 8
10. DAPR is using sidecar pattern 10
11. All difficult parts are handled by DAPR, the application is using the familiar protocols. 11
12. DAPR is sidecar so it listens on the same endpoint all the time: localhost. 12
13. Shall we start with demo? 13
14. Check the demo here: https://github.com/vranystepan/cncf-meetup-dapr-example-01 14
15. Also, check my blogpost: https://www.blog.vrany.dev/posts/2020-01-29-dapr-introduction/ 15
16. Thank you! Now let’s have some beer together ... Stepan Vrany Cloud Architect Twitter: @MstrsObserver LinkedIN: linkedin.com/in/stepanvrany 16