Extend Your Microservices With Pluggable Components Via Dapr
summary
Dapr 1.9 adds pluggable components so components no longer must be compiled in Go; they run as separate containers or local processes and register over Unix domain sockets using gRPC reflection. Operators keep the same component CRD (no new CRD), runtime is platform‑agnostic (Kubernetes or standalone), and planned SDKs cover .NET, Java, Python and Go. Demo shows a .NET memstore and a Java Discord binding persisting state successfully (over 100 upstream components, ~2,200 contributors).
AI-written summary · about
chapters (19)
- 0:00Introduction to Dapr
- 1:02What is Dapr
- 2:06Dapr’s APIs overview
- 4:11Dapr’s 100+ components
- 6:21Custom components before 1.9
- 7:46Pluggable components in 1.9
- 9:13Why no Go plugins
- 10:37How pluggable components work
- 12:41Kubernetes pluggable components
- 14:04Demo setup
- 15:12Building .NET component
- 18:42In-memory state store demo
- 19:55Dapr quick start
- 21:56Twitter to Discord demo
- 23:42Kubernetes deployment
- 25:50Discord message processing demo
- 26:52Code walkthrough of Discord binding
- 30:01Kubernetes manifests
- 31:04Q&A
related talks
54mDapr in Practice
57mDeveloping microservice applications with Dapr
21mShaping next generations of architectures with Dapr
31mBuilding scalable distributed systems powered by Dapr OSS.
46mDistributed Application Runtime
36mA Guide to Dapr: Open Source APIs & SDKs for Developers
46mDapr in Practice
56mBuilding Microservices With Dapr and .NET