As a consumer/prosumer/user of some IoT devices, the compute model I prefer is probably most closely aligned with what the author calls the "Fog" model. For devices at my home, I want:<p>* No data to leave my personal private network, except to third-party APIs for necessary information to fulfill my requests. If I have a smart agent device, for example, and I ask it to tell me the movies playing at my local theater, it is acceptable for an API request to go out to the cloud to fetch showtimes. But precisely that and only that.<p>* Computation runs on either the edge device itself or my local computing resources. Like many households, I have several "desktop class" PCs which each are more than capable of doing the kind of processing used by today's IoT use-cases. And like many <i>enthusiast</i> households, I have home servers as well, which are even more powerful. Despite several starts and stops in the space, I suspect eventually we will see home servers return as more people demand local processing and data autonomy.<p>* Data is stored either on the edge device or on my local computing resources (as above).<p>* Devices are available remotely via my home network's secure tunnel that is available anywhere on the Internet. (No specific requirements for the devices themselves.)
It took me far too long to work out that "fog" is a "cloud" that's right next to you, and hence "fog computing" is a local cloud. Haha. Of course, that made "mist", a thin fog (?) make sense too.