IoT Circus – Trapeze (In Cloud acrobatics).
summary
Architecture shows ingestion with IoT Hub per-device queues feeding a SQL-like Stream Analytics time-window layer that routes to Power BI or a database; an alternative message routes = predictable pricing path forwards filtered messages to Service Bus. Devices include Raspberry Pi running Windows 10 IoT Core with Arduino shields; demos emit accelerometer reaction times and expose flaky realities—transient time-sync errors, Chrome copy bug for connection strings, and missing crypto in open-source Arduino libs. Device twins hold desired/reported state and direct methods run only when devices are online.
AI-written summary · about
chapters (22)
- 0:00Intro
- 4:35The problem
- 6:35Message Queue
- 7:57Service Bus
- 9:50Realtime
- 13:10Demo
- 13:57Arduino Shield
- 14:49How much
- 15:37Its not impossible
- 16:50Security
- 17:33Windows Universal
- 18:19Blink
- 19:22IoT Core Device
- 20:45Remote Desktop
- 21:46Remote Client
- 24:20IoT Edge
- 27:07Azure IoT Hub
- 27:40Stream Analytics Job
- 29:58Power BI
- 30:58App whatsapp
- 32:18App shake
- 35:49Message Routes
related talks
25mKubernetes IoT Edge Working Group: Using Event Driven Architecture at Edge
35mIoT as a Platform: Scaling IoT Applications for the Enterprise Using Kubenernetes/OpenShift
34mStream Processing at the Edge with Apache Kafka
42mPrinciples and Patterns for Streaming Data Analysis
10mOpening Remarks
47mHow We Sought an IT Approach to a Diverse Fleet of Scooters
27mBridge Your IoT Leaf Devices to Local Clusters with Ease Using Akri...
39mIoT Application Running on KubeEdge + ARM Platform