
📡 IoT · Deployment · Pro
Where processing happens in an edge IoT setup: devices, an on-site edge server running containers, and the cloud for fleet management and long-term storage.
Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
Deployment for IoT edge computing: cameras and sensors on a site connect to an edge server running K3s with containers for data filtering, local ML inference (defect detection), a local time-series buffer and a local dashboard. The edge syncs summarised data to the cloud over 4G/fibre and keeps buffering during outages. The cloud hosts the fleet manager that deploys container updates, the data lake and central dashboards.
flowchart TB
subgraph Site[Factory / Store Site]
CAM[Cameras]
SEN[Sensors]
subgraph Edge[Edge Server - K3s]
FIL[Data Filter]
INF[ML Inference - defect detection]
BUF[(Local Buffer)]
LDASH[Local Dashboard]
end
end
subgraph Cloud[Cloud]
FLEET[Fleet Manager]
LAKE[(Data Lake)]
CDASH[Central Dashboards]
end
CAM --> INF
SEN --> FIL
FIL --> BUF
INF --> BUF
BUF --> LDASH
BUF -->|Summaries over 4G / fibre| LAKE
LAKE --> CDASH
FLEET -->|Container updates| EdgeHow sensor readings travel from devices to dashboards and alerts: MQTT ingestion, stream processing, time-series storage and anomaly detection.
How a new device joins the platform securely: claiming by the owner, certificate issue and its first connection to the MQTT broker.
A general-purpose IoT platform: device connectivity, device management, data processing, rules and the apps built on top.
How a smart home reacts to events: motion, door and temperature triggers run rules for lights, locks, AC and alerts.
How MQTT messaging works between devices, a broker and applications: connect, subscribe, publish with QoS, retained messages and last will.
Every state an IoT device goes through, from manufacture to decommissioning, including updates, faults and replacement.