There and Back Again: How Tunstall Healthcare Built an IoT Platform for Health Monitoring
summary
Builds an IoT platform using Mesos/DCOS on Azure with Marathon as the orchestrator and custom ARM/ACS templates instead of defaults to control VNETs, managed disks and mixed Linux/Windows nodes. Ingest pipeline treats device messages as opaque bytes, routes them through a payload pipeline to per-device/firmware metric extraction service that normalizes metrics for per-metric services and storage. Notes using private container registry, Marathon LB for SSL offload, role-based nodes for capacity, integration with legacy .NET, and a missing demo despite a 500 to 1,000,000 scaling claim.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:40Fredriks introduction
- 3:32What is Tunstall
- 4:14When is the market changing
- 6:36New markets
- 6:55What Tunstall did
- 7:30What is Evety
- 7:58What is Evety for
- 8:54Evety Architecture
- 11:07Plug and Play
- 11:34Frameworks
- 12:43Platform Architecture
- 15:06IoT Framework
- 16:19TSensor Data Architecture
- 19:08UNIX Architecture
- 19:55Metric Extraction Service
- 24:39Questions
- 25:36Lessons Learned
- 34:00Advice
- 38:32Data
related talks
55mIoT Solution Recipes - Beyond your first slice of Raspberry Pi
34mModern Data Platform, IoT & the Cloud -how...
32mConnecting Things Together, an IoT Data Protocol Story - Dave McAllister, Solace
42mBuilding IoT solutions using Azure IoT Edge
15mAzure IoT from the edge to ADX
59mDrinking a river of IoT data with Akka.NET
47mSolidifying industrial IoT with Azure IoT Hub
59mConnecting Devices in the Field to Microsoft Azure