Technical detail ยท Database Selection for IoT Workloads
Why a retry can change an average
The telemetry role accepts a duplicate sample after a gateway retry. If the store uses (device_id, event_time, sequence) as an idempotency key, the duplicate can update the same record or be ignored with an audit reason. If the key is only an auto-increment row id, the duplicate becomes a second reading and a one-hour average can be biased. A database category cannot answer that; the selected write path and key policy do.
The key must identify the logical sample across retries, rather than merely identify a newly inserted row. Check the actual write path rather than treating the database label as proof.