Techdays Helsinki - Creating the distributed apps of the future using dapr - Geert van der Cruijsen
4 likes491 views
The document discusses Dapr (Distributed Application Runtime), an event-driven, portable runtime designed to facilitate the building and running of microservices across various infrastructures. It emphasizes the importance of microservices architecture for improving productivity and scalability while providing essential building blocks like service invocation, state management, and publish-subscribe messaging. Additionally, it highlights Dapr's compatibility with multiple programming languages and its potential to simplify the development process for distributed systems engineers.
![Microservice building blocks
State management
Service A Dapr Sidecar
POST http://localhost:3500/v1.0/state/statestoreName
[{
"key": “order1",
"value": {
"Order": {...}
}
}]
State stores
GET http://localhost:3500/v1.0/state/statestoreName/order1
{
"Order": {...}
}
@geertvdc](https://image.slidesharecdn.com/tdhelsinki-creatingthedistributedappsofthefutureusingdapr-geertvandercruijsen-200312112746/85/Techdays-Helsinki-Creating-the-distributed-apps-of-the-future-using-dapr-Geert-van-der-Cruijsen-27-320.jpg)
Techdays Helsinki - Creating the distributed apps of the future using dapr - Geert van der Cruijsen
- 1. Build the distributed apps of the future using Dapr Geert van der Cruijsen @geertvdc
- 2. Geert van der Cruijsen @geertvdc Cloud Native Architect Full Cycle Developer DevOps Consultant
- 3. Some time ago this definition was someone who was able to do both backend and frontend development Full stack Developers 2010 Frontend Backend @geertvdc
- 4. Now we want teams to be autonomous. Focussing on the full product lifecycle, building & running it! Full stack Developers now Frontend Backend Pipelines Containers Monitoring Cloud infra Databases Cost Networks Security @geertvdc
- 5. The goal of these autonomous teams was enabling them to be more productive, not having to wait on others. But we can’t be masters of all these traits. Is there a middle ground? Conflict! Frontend Backend Pipelines Containers Monitoring Cloud infra Databases Cost Networks Security @geertvdc
- 6. What the business wants Scalable Fast to Market Resilient to failure Secure Cheap Easy to Build & run @geertvdc
- 7. Current state of development Business features All other stuff we spend time on as developers @geertvdc
- 8. Why Dapr? Business features All other stuff we spend time on as developers @geertvdc
- 9. An event-driven, portable runtime for building microservices on cloud and edge. @geertvdc
- 10. Migrating existing applications to a microservice architecture Making microservices easier for every language or platform Enable Microservices on every infrastructure and decoupling dependencies @geertvdc
- 11. Dapr building blocks Runs on multiple environments for cloud, on- prem, and small-edge including any KubernetesRuns everywhere Make it easy for developers to create microservice applications without being an expert in distributed systems, including migrating existing code Microservice Building Blocks Developer first, standard APIs used from any programming language or frameworkSidecar Architecture @geertvdc
- 13. Sidecar Architecture Service-to- service invocation State management Publish and subscribe Resource bindings and triggers Actors Distributed tracing Extensible HTTP API gRPC API Application code @geertvdc
- 14. Sidecar Architecture Service-to- service invocation State management Publish and subscribe Resource bindings and triggers Actors Distributed tracing Extensible HTTP API gRPC API Any code or framework… Functions S e r v i c e s w r i t t e n i n .NET Core Application code @geertvdc
- 15. Sidecar Architecture HTTP / GRPC http://localhost:3500/v1.0/state/order http://localhost:3500/v1.0/invoke/servicea/method/createorder Service A Dapr Sidecar @geertvdc
- 16. Application Sidecar Architecture – Self hosted Service A Dapr Sidecar Service B aaa Dapr Sidecar State stores Publish and subscribe @geertvdc
- 17. Kubernetes Sidecar Architecture - Kubernetes Placement Sidecar Injector Operator @geertvdc
- 18. Kubernetes Sidecar Architecture - Kubernetes Placement Sidecar Injector Operator Pod Service A Pod Service B @geertvdc
- 19. Kubernetes Sidecar Architecture - Kubernetes Placement Sidecar Injector Operator Pod Service A Dapr Sidecar Pod Service B Dapr Sidecar @geertvdc apiVersion: apps/v1 kind: Deployment metadata: name: orderapi labels: app: orderapi spec: replicas: 1 selector: matchLabels: app: orderapi template: metadata: labels: app: orderapi annotations: dapr.io/enabled: "true" dapr.io/id: "orderapi" dapr.io/port: "80" dapr.io/config: "tracing" dapr.io/log-level: "debug" spec: containers: - name: orderapi image: xpiritbv/dapr-demo-orderapi:lates env: - name: DAPR_HTTP_PORT value: "3500" - name: DAPR_STATESTORE value: "statestore" ports: - containerPort: 80 imagePullPolicy: Always
- 20. Kubernetes Sidecar Architecture - Kubernetes Placement Sidecar Injector Operator State stores Publish and subscribe Pod Service A Pod Service B @geertvdc Dapr Sidecar Dapr Sidecar apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: statestore spec: type: state.redis metadata: - name: redisHost value: redis-master:6379 - name: redisPassword value: *****
- 21. Kubernetes Sidecar Architecture - Kubernetes Placement Sidecar Injector Operator State stores Publish and subscribe Pod Service A Dapr Sidecar Pod Service B Dapr Sidecar @geertvdc
- 23. Runs Everywhere You don’t have to use this in a green field scenario. Dapr enables you to pick and choose whatever components you want to use. Connect Legacy Almost every programming language has support for HTTP or GRPC. You do not need any SDK to work with Dapr HTTP / GRPC There are SDKs in many languages to make the life of developers even easier. C#, Javascript, Java, Rust, Go, C++, Python SDKs in multiple languages @geertvdc
- 25. Microservice building blocks Distributed tracing See and measure the message calls across components and networked services Actors Encapsulate code and data in reusable actor objects as a common microservices design pattern Resource bindings and triggers Trigger code through events from a large array of inputs Output bindings to external resources including databases and queues Publish and subscribe Secure, scalable messaging between services State management Create long running, stateless and stateful services Service-to- service invocation Perform direct, secure, service- to-service method calls Service invocation @geertvdc
- 26. Microservice building blocks Service invocation Service A Dapr Sidecar Service BDapr Sidecar POST http://localhost:3500/v1.0/invoke/ServiceB/method/MethodA POST http://localhost:80/MethodA @geertvdc
- 27. Microservice building blocks State management Service A Dapr Sidecar POST http://localhost:3500/v1.0/state/statestoreName [{ "key": “order1", "value": { "Order": {...} } }] State stores GET http://localhost:3500/v1.0/state/statestoreName/order1 { "Order": {...} } @geertvdc
- 28. Publish Message bus Subscribe Microservice building blocks Publish & subscribe Service A Dapr Sidecar Service BDapr Sidecar POST http://localhost:3500/v1.0/publish/topic { “OrderId”: 123, “CustomerId”: 555, ... } POST http://localhost:80/v1.0/topic { “OrderId”: 123, “CustomerId”: 555, ... } GET http://localhost:80/dapr/subscribe { “topic” } @geertvdc
- 29. Microservice building blocks Distributed tracing Service A Dapr Sidecar Service BDapr Sidecar OpenCensus @geertvdc
- 30. Microservice building blocks Distributed tracing Service A Dapr Sidecar Service BDapr Sidecar … @geertvdc
- 31. Microservice building blocks Distributed tracing @geertvdc
- 32. Microservice building blocks Resource Bindings & Triggers @geertvdc Service ADapr Sidecar Triggers POST http://localhost:80/Trigger { “ItemId”: 555999332211345, “Quantity”: 1, ... }
- 33. Microservice building blocks Resource Bindings & Triggers @geertvdc Dapr Sidecar Triggers Dapr Sidecar Bindings Service A POST http://localhost:3500/v1.0/bindings/twilio { “Email”: “[email protected]”, “topic”: “sent from Dapr binding”, ... }
- 34. Microservice building blocks Actors @geertvdc Stateful microservices Virtual actors Distribution & failover Turn based concurrency Build on Service Fabric knowledge Shoppingcart 1234 Shoppingcart 5678 Shoppingcart 4321 Shoppingcart 8765 AddItem AddItem AddItem AddItem
- 35. Microservice building blocks Actors @geertvdc Service A Dapr Sidecar Placement Service Kubernetes Node 1 Kubernetes Node 2 Pod Sidecar Cart 1 POST http://localhost:3500/v1.0/actors/CartActors/Cart1/method/AddItem { “ItemId”: 555999332211345, “Quantity”: 1, ... } POST http://localhost:80/AddItem { “ItemId”: 555999332211345, “Quantity”: 1, ... } Pod Sidecar Cart 2
- 36. Microservice building blocks Actors @geertvdc Service A Dapr Sidecar Placement Service Kubernetes Node 1 Kubernetes Node 2 Pod Sidecar Cart 1 Pod Sidecar Cart 2
- 37. Demo Order API Building an order application Loyalty Service ShippingCost Service Generate Orders Message bus Shipping Service Shipping Service State Store @geertvdc
- 38. https://github.com/xpiritbv/dapr-workshop/ Demo Building an order application @geertvdc
- 39. Wrap up @geertvdc Dapr will make your life easier as a distributed systems engineer Go give it a try. It’s free & open source. Lot’s of samples, good docs & active community / developers Let the community know what you like & dislike through Github