Shaping next generations of architectures with Dapr
summary
Dapr claims a portable, language agnostic runtime that implements the sidecar pattern and provides service invocation, state, pub/sub, actors and tracing via standard HTTP/gRPC APIs. A live demo runs a NodeJS app on 3000 while Dapr answers on 3500 port, a Python client loops creating orders through Dapr, and logs show service discovery and component loading succeeding. Local install spins up a default Redis state store container, CLI uses dapr run --app-id, and the ecosystem lists 100+ components.
AI-written summary · about
chapters (12)
- 0:00Introduction and Speaker Background
- 0:12Understanding Microservices Architecture
- 0:51Challenges with Microservices
- 2:02Introduction to Dapper
- 2:18Dapper's Objectives and Features
- 3:32Dapper's Sidecar Pattern
- 4:57Service Invocation and State Management with Dapper
- 7:45Hands-On Example with Dapper
- 15:41Deploying Dapper in Production
- 17:17Dapper Components and Configuration
- 19:49Dapper in the CNCF Ecosystem
- 20:22Conclusion and Contact Information
related talks
54mDapr in Practice
31mBuilding scalable distributed systems powered by Dapr OSS.
57mDeveloping microservice applications with Dapr
46mDistributed Application Runtime
49mStart Building Distributed Applications with Ease Using Building Block APIs
46mDapr in Practice
01h 06mBuild powerful distributed applications with Dapr and .NET
36mA Guide to Dapr: Open Source APIs & SDKs for Developers