← Back to the chapter · Next detail →

Technical detail · Edge, Fog, and Cloud: Operating at Scale

Peer overlays and membership

9.7.1 Peer Overlays as Fog Building Blocks

Some fog designs borrow the old peer-to-peer lesson: a large system can spread load by letting many edge participants exchange pieces of work, cache state, or distribute content instead of forcing every transfer through one central server. BitTorrent-style swarms, tree overlays, and multi-tree overlays are useful analogies because they make the tradeoff visible. They can improve scale and resilience, but they also introduce churn, neighbor choice, duplicate traffic, trust questions, and evidence that must be observable when a peer disappears.

Use a peer overlay only when the deployment record names the owner of membership, the admission rule, the data each peer may hold, the fallback route when the overlay fragments, and the measurement that proves the overlay is helping. A firmware cache among gateways, a local model-update mirror, or a site-to-site evidence replication path may be reasonable. A safety command path, credential update, or audit ledger usually needs stronger authority than an opportunistic swarm can provide.

← Back to the chapter · Next detail →