Skip to content
Historical revision — this record as it stood on 1 July 2026, not the current version. View the current record →

Fog Computing

Fog computing — also called fog networking or fogging — is a distributed computing architecture that uses edge devices to carry out a substantial amount of computation, storage, and communication locally, with data routed over the internet backbone only when required. The term was coined by Cisco in 2012 to describe an approach to distributed computing that addresses the limitations of cloud computing for real-time, latency-sensitive, and bandwidth-constrained IoT applications.

The "fog" metaphor refers to cloud-like properties brought closer to the "ground" — to IoT and edge devices that generate data. Where cloud computing centralizes processing in remote data centers, fog computing distributes it to computing units co-located with data-generating devices, so that processed rather than raw data is forwarded upstream and bandwidth requirements are reduced.

Concept

The fog computing paradigm emerged from a specific problem: the proliferation of Internet of Things devices generating voluminous sensor data that, if forwarded entirely to cloud data centers for processing, would exceed available backbone bandwidth and introduce latency incompatible with real-time applications. The approach behind fog computing is to perform as much processing as possible using computing units co-located with the data-generating devices, so that the data reaching the backbone is already processed and the round-trip latency between sensor input and action is minimized.

An additional advantage is that processed data is most likely needed by the same devices that generated it: by processing locally rather than remotely, the latency between input and response is minimized without requiring any change in the cloud architecture. The idea itself is not new — in non-cloud scenarios, special-purpose hardware (signal-processing chips performing Fast Fourier Transforms) has long been used to reduce latency and CPU burden. Fog computing extends this principle to programmable, networked computing infrastructure.

Fog computing is characterized by: proximity to end users; dense geographical distribution; context-awareness regarding computational and IoT resources; latency reduction and backbone bandwidth savings; and redundancy in case of failure. It also enables edge analytics and stream mining, which cloud-based analytics cannot perform at the required latency. Fog nodes can provide security for resource-constrained IoT devices by performing cryptographic computations that the devices themselves cannot execute.

Architecture

A fog computing architecture consists of a control plane and a data plane. On the data plane, fog computing enables computing services to reside at the edge of the network as opposed to servers in a data center. Fog nodes — intermediate computing units between edge devices and the cloud — receive data from edge devices, process it locally, and forward only the relevant results or aggregated summaries to the cloud.

The NIST Special Publication 500-325 (March 2018) formally defines fog computing as "a horizontal, physical or virtual resource paradigm that resides between smart end-devices and traditional cloud computing or data center" and states that this paradigm "supports vertically-isolated, latency-sensitive applications by providing ubiquitous, scalable, layered, federated, distributed computing, storage, and network connectivity."

NIST further distinguishes fog computing from edge computing: in the theoretical model, fog computing nodes are physically and functionally operative between edge nodes and centralized cloud. "Fog computing is most distinguished by distance from the edge." For smaller deployments, fog and edge computing are often used interchangeably; for large-scale smart city deployments, fog computing is a distinct intermediate layer.

Comparison with cloud and edge computing

Both cloud computing and fog computing provide storage, applications, and data to end users. Fog computing is closer to end users than cloud computing and provides wider geographical distribution. Fog computing implies distribution of communication, computation, storage resources, and services on or close to devices and systems in the control of end users.

Fog computing is a medium-weight, intermediate level of computing power. Rather than a substitute for cloud computing, fog computing serves as a complement — offloading latency-sensitive or bandwidth-intensive processing locally while relying on cloud infrastructure for storage, analytics, and non-time-critical processing. Fog computing is more energy-efficient than cloud computing when aggregated over large IoT deployments, because the elimination of unnecessary data transit reduces both bandwidth costs and the energy consumed by data center processing of irrelevant raw data.

History and standards

The term "fog computing" was first developed by Cisco in 2012. On 19 November 2015, Cisco Systems, ARM Holdings, Dell, Intel, Microsoft, and Princeton University founded the OpenFog Consortium to promote the development and adoption of fog computing. The IEEE adopted fog computing standards proposed by the OpenFog Consortium; the primary standard is IEEE 1934-2018.

The IoT use cases supported by fog computing include connected vehicles, wearable health monitoring devices, augmented reality, and smart drone swarms. The US Navy's Space and Naval Warfare Systems Command (SPAWAR) has prototyped scalable, secure Disruption Tolerant Mesh Network implementations using fog computing architecture to protect strategic military assets including stationary and mobile IoT systems.

ISO/IEC 20248 provides a method whereby data from objects identified by edge computing using Automated Identification Data Carriers (AIDC) — barcodes and RFID tags — can be read, interpreted, verified, and made available into the fog and on the edge even when the AIDC tag has moved on.


cites: edge-computing, application-programming-interface, computer-appliance, virtual-appliance

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. See TRADEMARK.md in this repository for the full trademark notice.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →