📡 IoT · C4 Architecture · Pro
IoT Platform Reference Architecture
A general-purpose IoT platform: device connectivity, device management, data processing, rules and the apps built on top.
C4 Architecture diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
What this diagram shows
- Devices connect over MQTT with per-device certificates
- Device twin keeps desired and reported state
- Rules engine turns telemetry into actions and alerts
Prompt used
IoT platform architecture: devices connect over MQTT/TLS to a device gateway. Platform services: device registry and provisioning, device twin (desired vs reported state), telemetry ingestion into a time-series DB, a rules engine for alerts and actions, OTA firmware service. Customer apps and dashboards use a REST API; data is exported to a data lake for analytics.
Mermaid code
C4Container
title IoT Platform
Person(user, "Customer / Operator", "Monitors devices")
System_Ext(devices, "Devices", "Sensors and controllers")
System_Boundary(iot, "IoT Platform") {
Container(gw, "Device Gateway", "MQTT broker", "Device connections")
Container(reg, "Device Registry", "Go", "Identity and provisioning")
Container(twin, "Device Twin", "Go", "Desired vs reported state")
Container(ing, "Telemetry Ingestion", "Kafka + Flink", "Streams readings")
ContainerDb(ts, "Time-series DB", "TimescaleDB", "Telemetry")
Container(rules, "Rules Engine", "Java", "Alerts and actions")
Container(ota, "OTA Service", "Go", "Firmware updates")
Container(api, "Platform API", "REST", "Apps and dashboards")
}
Rel(devices, gw, "MQTT/TLS")
Rel(gw, reg, "Authenticates")
Rel(gw, ing, "Telemetry")
Rel(ing, ts, "Stores")
Rel(ing, rules, "Evaluates")
Rel(rules, twin, "Sets desired state")
Rel(twin, gw, "Commands")
Rel(ota, gw, "Firmware")
Rel(user, api, "Uses")
Rel(api, ts, "Queries")Related templates
IoT Telemetry Data Pipeline
How sensor readings travel from devices to dashboards and alerts: MQTT ingestion, stream processing, time-series storage and anomaly detection.
IoT Device Provisioning Sequence
How a new device joins the platform securely: claiming by the owner, certificate issue and its first connection to the MQTT broker.
IoT Edge Computing Deployment
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.
Smart Home Automation Flow
How a smart home reacts to events: motion, door and temperature triggers run rules for lights, locks, AC and alerts.
MQTT Publish/Subscribe Messaging
How MQTT messaging works between devices, a broker and applications: connect, subscribe, publish with QoS, retained messages and last will.
IoT Device Lifecycle
Every state an IoT device goes through, from manufacture to decommissioning, including updates, faults and replacement.