← Back to the chapter · Previous detail · Next detail →

Technical detail · IoT Glossary: Q-R

State ownership and operational trade-offs

Many Q-Z terms are operational contracts. MQTT QoS 1 can redeliver a message, so consumers still need deduplication or idempotent state changes. QoS 2 narrows one MQTT duplicate-delivery path, but it does not make a physical actuator command safe by itself. TLS protects transport only when certificates, hostnames, time, keys, and trust stores are correct.

Time-series terms carry similar boundaries. Sampling rate changes what a sensor can represent. Schema changes what a downstream service can trust. Retention policy changes what an incident review can reconstruct. Downsampling changes which anomalies survive long-term storage.

The hidden technical detail is usually state ownership. A broker owns session state, inflight packet identifiers, retained messages, subscriptions, and wildcard matching. Firmware owns local sampling, UART or SPI timing, retry queues, and command execution. A gateway or border router owns protocol adaptation, Thread-to-IP forwarding, Zigbee coordinator state, Z-Wave regional behavior, or 6LoWPAN compression and fragmentation. A data platform owns timestamp normalization, schema compatibility, retention, rollups, and alert queries.

Because those owners differ, one Q-Z fix can create another Q-Z failure. Raising MQTT QoS can increase radio wake time and duplicate-handling requirements. Extending TSDB retention can increase storage cost while still losing high-frequency anomalies if downsampling is too aggressive. Tightening TLS or token lifetime can break devices with bad clocks or unreachable renewal paths. Moving from Wi-Fi to Thread or Zigbee can reduce power, but it introduces mesh-health, border-router, coordinator, channel, and certification constraints.

A rigorous capstone treats late-alphabet vocabulary as a runbook checklist: what state exists, where it is stored, how it expires, who can rotate it, how duplicates are detected, how failures are retried, and which evidence would prove the system behaved correctly after an outage or upgrade.

For capstone work, use Q-Z terms to assign operational responsibility: which firmware task, broker, route, gateway, database, dashboard, alert rule, certificate store, or support process owns the next check?

← Back to the chapter · Previous detail · Next detail →