Defining IoT — Device, Gateway, Cloud

easy

Learn with your AI

Pick a depth. Each prompt opens in your AI pre-loaded with the lesson. Click a row to preview the prompt.

Or teach me the whole lesson:

Why this matters

The phrase 'Internet of Things' is misused to mean everything from a Wi-Fi lightbulb to industrial SCADA. Before you build anything, you need a precise mental model: a device that senses or acts on the physical world, a gateway/network path that aggregates and routes its data, and a cloud (or backend) layer that stores, analyzes, and exposes that data to humans and other systems. Without this three-tier picture you'll over-engineer trivial cases and under-architect the hard ones — sticking a cellular modem on a $5 sensor that only ever talks to a hub three metres away, or shipping a 'cloud-native' security camera that drops every clip the moment Wi-Fi blips.

Demo

The canonical three-tier IoT architecture.

Try it yourself

Pick one IoT product you own (smart bulb, fitness tracker, video doorbell, smart speaker) and decompose it into the three tiers: where does each tier physically live, and what protocol connects them?
Identify a product where the three tiers are collapsed (e.g., a Wi-Fi sensor talks directly to the cloud with no separate gateway). Write one sentence on what design constraint forced or allowed that collapse.
Open your phone's Bluetooth settings and list every device it has ever paired with. For each, identify whether your phone acts as a gateway, the device itself, or both.

References

[ DEVICE ] [ GATEWAY ] [ CLOUD ] ───────── ────────── ───────── Sensors ──┐ ┌── Aggregates messages from ┌── Stores telemetry Actuators ─┤ Reads / writes │ many devices │ (time-series DB) MCU/SoC ─┤ the physical world │ │ Radio ─┤ (1 Hz to 10 kHz) │── Translates protocol │── Exposes APIs Battery ─┘ │ (BLE/Zigbee → MQTT/HTTPS) │ (REST / GraphQL) │ │ │ │── Buffers when uplink down │── Runs rules, │ (BLE / Zigbee / │ │ ML, dashboards │ LoRa / Wi-Fi) │── Enforces local policy │ ▼ │ (LAN-only commands, │── Pushes commands │ privacy filters) │ back to devices │ │ └── Optional: edge inference │── User app / web └── (dashboards, mobile apps) COLLAPSED ARCHITECTURES (common in practice): • A Wi-Fi smart plug talks MQTT directly to the cloud — the home router is the gateway in the network sense, but the plug is its own "gateway" in the protocol sense. • An industrial PLC reads 200 modbus sensors and uplinks one summary record — the device IS the gateway. • A BLE-only fitness tracker uses your phone as a transient gateway whenever you're near it; offline storage on the device must bridge the gaps.