There are more IoT protocols out there than most teams will ever need. That sounds overwhelming until you realize most connected products only use two or three; one for local communication, one for cloud connectivity, and sometimes one for device management.
The problem is not the number of options. The problem is that the protocol you pick at the design stage gets baked into your firmware, your cloud pipeline, and your data model. Change it later and you are rewriting half of your stack.
Here is a practical breakdown of the protocols that matter for most developers building connected products today.
The Three Layers You Are Choosing Across
IoT protocols sit in three distinct layers, and you typically pick one from each:
