Fog Computing vs Edge Computing: What Is the Difference?

Edge computing means processing data as close as possible to where it is created: inside a smart camera, on a computer bolted to a machine, or in a gateway in the same cabinet as the sensors. Fog computing describes a layer above that, made of local servers, gateways and network nodes that sit between many edge devices and the cloud, usually on the same site or local network.

The term fog computing was introduced by Cisco researchers in 2012 to describe a cloud brought down close to the ground. The OpenFog Consortium, founded in 2015, produced a reference architecture that was adopted as IEEE 1934 in 2018, and NIST published a fog computing conceptual model, SP 500-325, the same year. Edge computing is the older and wider term, and the one most vendors now use for both layers.

So the difference is mainly one of position and scope. Edge works on one device’s data. Fog works across many devices and coordinates what goes to the cloud.

A three-layer system splits the work by how quickly a decision is needed and how much data each layer can afford to handle.

In real deployments the layers overlap, but the typical differences are clear.

A fog layer earns its place when a site has many edge devices producing more data than the internet link can carry, when decisions need data from several machines at once, or when the site must keep running through an outage. Its costs are more hardware on site, another layer to patch and secure, and the skills to manage it. Small deployments often skip it and send edge results straight to the cloud.

A factory shows how the layers fit together. Each production line has an edge computer running vision inspection and reading its PLC, deciding pass or fail in milliseconds. A fog server in the plant room collects results and machine data from every line, runs the site’s dashboards and maintenance alerts, and holds a week of history. Once an hour it sends summaries to the cloud, where the company compares plants and retrains its inspection models.

Smart city systems, among the most common fog computing applications, follow the same shape. Cameras at junctions count vehicles and detect incidents at the edge, a roadside or district server coordinates signal timing across a corridor, and the cloud plans the network. Oil and gas fields, wind farms and rail depots use the fog layer to keep working through slow or intermittent links.

The edge layer is where edge AI usually runs, because inference needs the raw images or signals before they are reduced.

The architecture is widely used; the name less so. Most vendors and standards groups now describe the same layers as the device edge, the on-premises edge and the cloud, and the OpenFog Consortium merged into the Industrial Internet Consortium in 2019. When someone specifies an on-premises edge server that aggregates many devices, they are describing a fog node. In the USA and the US alike, buyers more often search for edge computing, while fog still appears in research, telecoms and smart city work.

The hardware follows the layer. At the device edge, embedded PCs and industrial IoT gateways sit in cabinets and on machines. At the fog layer, edge AI servers and short-depth rack servers sit in plant rooms and comms rooms. Our guide to AMD EPYC Embedded for edge servers covers the processor options at that layer.

We supply and integrate edge computers and edge servers as standard, with the storage, networking and operating system each layer needs prepared before the systems ship.