The layer between edge and cloud.
WHAT IT DESCRIBES
An intermediate layer between devices and central facilities, providing computation and storage closer than the cloud but broader than a single device.
WHY THE DISTINCTION EXISTS
Devices are too constrained for some work, and the cloud is too distant for latency-sensitive work.
WHAT THAT LAYER DOES
Aggregates data from many devices Filters and summarises before transmission Performs local analysis and control Provides local storage
WHY AGGREGATION MATTERS
Transmitting every reading from every sensor is expensive and usually unnecessary.
WHAT TO TRANSMIT INSTEAD
Summaries, exceptions and events.
WHAT THAT SAVES
Bandwidth, cost, and central processing.
WHAT TO KEEP LOCALLY
Raw data, briefly, for investigation.
WHAT THE HIERARCHY LOOKS LIKE
Devices, gathering A local layer, processing and controlling A central layer, analysing across locations
WHAT DECIDES WHERE WORK BELONGS
Latency requirement Data volume Whether it must work while disconnected Privacy constraints
WHAT TO AVOID
Treating the distinction as more important than it is.
WHY
The terms overlap, and what matters is where the work actually belongs.
