Zero Pain Microservice Development and Deployment with Dapr and KubeVela
summary
Alibaba claims developers only change app code while the platform provisions infra by combining KubeVela and Dapr, using a sidecar-based approach and templated capabilities (Helm, Kustomize, Terraform). Production footprint is over 10 platforms and thousands of apps. A concrete artifact, the matrix trait, auto-wires a Dapr sidecar and exports metrics to an OpenTelemetry collector; that pipeline runs in production and feeds dashboards (Grafana or cloud vendor services).
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:14About me
- 0:37Content
- 1:12K8s Resource Composition
- 1:38k8s-sig Application
- 2:09Helm Chart
- 2:59In-House CRD
- 3:53What We Need
- 5:53KubeVela Architecture
- 6:43KubeVela Application
- 7:32ComponentDefinition
- 8:16TraitDefinition
- 10:02Other Features
- 10:43Dapr Overview
- 11:31Alibaba Contrib/Adoption
- 12:00Case Study: Application Monitoring
related talks
57mDeveloping microservice applications with Dapr
24mSponsored Session: Platform Engineering with KubeVela: Shipping Apps the...
56mBuilding Microservices With Dapr and .NET
54mDapr in Practice
01h 03mDeveloping microservices like a boss with Dapr and Azure Container Apps
22mBuilding Real-World Applications with Dapr: A Startup Developer's Journey
28mMicroservices Made Easy!
01h 01mUnleashing the Power of Microservices with Dapr and Azure Container Apps