← Back to the chapter · Previous detail · Next detail →

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

Client-driven control authority

9.7.2 Client-Driven Control Loops

Client-driven fog control moves part of the control and configuration loop toward clients, gateways, or near-user edge devices. That can reduce cloud dependence and react faster to local congestion, but it changes who is allowed to infer network state. A client may estimate congestion from delay, round-trip time, duplicate acknowledgements, packet loss, queue growth, or local radio measurements. Those signals are useful only when the design records their sampling window, expiry, hysteresis, and the action they are allowed to trigger.

The review question is not “can the client detect congestion?” It is “what can this client safely change after detecting it?” Reducing a report rate, choosing a less congested local path, switching to a cached result, or delaying a noncritical upload may be safe. Reassigning site authority, changing another device’s configuration, or hiding a persistent outage from operators is not. Client-driven control should therefore publish local evidence upward when connectivity returns, so cloud and operations records can see which decisions were made under local authority.

← Back to the chapter · Previous detail · Next detail →