While I appreciate the intent, the problem with all of these &quot;IoT frameworks&quot; is that they were designed by people with a <i>device view</i>. They are oblivious to, and typically poor for, what the aggregate architectures look like at scale where you bring all of this IoT data together either logically or physically.<p>To get in the right frame of mind for IoT platform design, think of a mobile carrier network with 100 million subscribers as a single geographically-distributed computing system that extends all the way to the mobile phone. The complex topological constraints implied by that means, from top to bottom, making systems scale requires software architectures that are substantially different from the web. For starters, they need to be deeply aware of the spatial, temporal, and topological relationships between nodes, which is much closer to massively parallel computing models than a traditional web-oriented distributed system. (In massively parallel systems computation is literally and noticeably relativistic, and with topologies that place complex restrictions on how computations can flow between compute nodes. If you do not explicitly account for this in your architecture, scaling will be significantly sublinear.)<p>This leads to the situation today where you have a dozen different &quot;IoT platforms&#x2F;protocols&quot; all being furiously pushed into the market as <i>de facto</i> or actual standards, but if you look at the companies with real experience building large-scale IoT architectures they use none of it because it doesn&#x27;t deliver for real-world systems. A lot more thought needs to go into the <i>requirements</i> for an IoT platform; it looks nothing like a web architecture.