Which IoT protocol to choose
Short answer
The most-used IoT protocols are MQTT (pub/sub, lightweight, production standard), CoAP (UDP, ultra-constrained), HTTPS (familiar, heavier) and LwM2M (full device management with OTA). Pick based on power, bandwidth, criticality, and whether you need device orchestration.
Quick matrix by use case
Pub/sub with decent bandwidth and kept session → MQTT. One-shot message over UDP, extreme battery → CoAP. Simple daily report against REST API → HTTPS. Fleet management with OTA, firmware, configuration → LwM2M. Enterprise integration backbone → AMQP.
Power and overhead
CoAP is lightest (over UDP, minimal headers). MQTT follows (over TCP, low overhead). HTTPS adds handshakes and headers — convenient but expensive on data. LwM2M sits on top of CoAP and adds orchestration.
Firmware OTA and management
If you need to update firmware, rotate keys, and reconfigure devices at scale, LwM2M is built for it. MQTT requires you to build that layer. For serious fleets: LwM2M or MQTT + management broker.
- MQTT: IoT standard
- CoAP: ultra-efficient
- HTTPS: simple, heavy
- LwM2M: full management
- AMQP: enterprise integration
IoT protocol decision tree
Download the tree (1-page PDF): answer 5 questions, get the right protocol per use case.
Frequently asked questions
Can I mix protocols?+
Yes. Common pattern: MQTT for telemetry, LwM2M for management and OTA, HTTPS for admin endpoints. A good IoT platform orchestrates that.
CoAP in production?+
Yes, in niches (NB-IoT metering, ultra-low-power sensors). Outside that, MQTT usually wins on ecosystem.
What about WebSockets?+
WebSockets tunnels many protocols (MQTT, STOMP) through proxies and restrictive corporate firewalls. Useful when the device sits behind tough NAT.
You might also like