In my CBT Nuggets course – Cisco CCIE Evolving Technologies – we tackle IoT in some decent depth as required of us by Cisco Systems. In this post, I wanted to warm you up for some of that by introducing you to two terms – Fog and Edge Computing.
These days, all we seem to hear about is cloud computing. And cloud computing certainly plays into IoT, as we’ll discuss. But there’s also edge and fog computing that is quite popular when it comes to the Internet of Things.
Let’s actually start with fog computing. You’re going to note that both fog and edge computing refer to having processing taking place that is much closer to the actual devices than the cloud. So think about the cloud, public or private. It’s kind of way up there in the stack.
So we might have all of these IoT devices running at a local location. And we want computing to take place closer to them than that faraway cloud. So fog computing is an example of this. And where the processing takes place with fog computing is in the network devices, such as gateways and routers and switches that make up the network.
If we can do some of the processing there, closer to the actual devices– thus, the concept of fog, which is closer to the ground instead of a full-blown cloud– then this is going to do wonders for the IoT implementation. Typically, notice that we’re processing or storing information for the higher levels and those higher levels might actually exist in the cloud. We often do this in a hierarchical type format.
An example I want to give you is temperature monitoring. So let’s say we have these IoT devices that are monitoring temperatures.
If we can have intelligence in our network devices and do some fog computing, one of the things that we might have those devices do is see, inside the data, if there’s actually been any temperature change and, if there hasn’t been a temperature change, to stop the flow right there. Otherwise, the device can alert the cloud, and then have the cloud trigger some type of temperature alarm.
So in this case, it’s reducing the amount of bandwidth we consume, and even reducing processing that we might need to do somewhere else in the stack, based on the fact that there’s been no temperature change.
Edge computing takes the computing horsepower or the processing horsepower and it moves it even closer to the smart things by actually building the intelligence into the smart things themselves. We sometimes refer to this as mist computing because it’s even closer to the actual devices than fog computing. Typically, it’s intelligence built into those smart devices.
Notice that we could structure this in a very hierarchical fashion. If it’s time-sensitive information, we should be analyzing it as close to the source as possible. We could then use our fog nodes, things like gateways and network devices, that can aggregate the information taken from the actual smart things themselves.
Notice you might want to store information locally in your data center initially and then move it to the cloud for the ultimate storage and for more long-term things, like trend analysis and more detailed analysis. This might even include some machine learning.
So remember, fog computing is intelligence and processing that we’re going to do pretty close to the devices themselves. But edge computing would be an IoT reference, where we’re even closer to those devices. In fact, this is often implemented in the devices themselves, making them smart devices that are capable of computing and processing.
Thanks for reading!
Interested in more great information on this fascinating topic? Check out this article:
Do We Need To Replace The Cloud With Edge Computing?