Cloud Native Digital Twins
summary
Shows a working cloud-native pipeline: devices publish telemetry to Kafka, Knative Eventing sequences call a small converter service (Quarkus or Rust) that maps payloads via Warto schemas into CloudEvents and posts them to an Eclipse Ditto digital twin endpoint. Drogue Cloud provides a device registry as source of truth with controllers that reconcile state (desired vs actual) and supports MQTT/HTTP bridges. Rust is used for tiny, fast serverless containers and the example end‑to‑end mapping and Ditto ingestion is implemented.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:25Frame the problem
- 4:10Digital Twins
- 5:37Reconciliation Loop Pattern
- 7:37Eclipse
- 9:40Eclipse Worker
- 10:14Modify commands
- 11:39Introduction to Cloud Native
- 12:43What is Cloud Native
- 17:37What is the idea behind the Digital Twins
- 19:04Why Rust
- 21:44Cloud Events
- 22:37Cloud Events API
- 23:56Serverless Infrastructure
- 25:14Demo
- 28:52Control Plane
- 31:17Devices
- 31:50Conclusion
related talks
36mBuilding Digital Twins for DFDS With Crossplane and Kubernetes
01h 00mWorkshop: Eclipse Ditto - Digital Twins as Part of an Open IoT Platform
28mCloud Agnostic Design Patterns and Tips
31mCloud native: the cattle the pets and the germs
35mComplete Idiot's Guide to Cloud Native
40mThinking Cloud Native, CloudEvents Future
28mConnectivity Patterns for Cloud Native Applications
49mApplications architecture spanning multiple clouds