← Back to the chapter · Previous detail
Technical detail · Edge Placement and Cost Contracts
Tail latency and diagnostic evidence
Latency risk is about worst-case behavior, not average behavior. A cloud path with a 150 ms average can spike above a second during congestion, DNS failures, cellular handover, or regional service incidents. If the control loop fails when the tail is bad, the function belongs locally even when cloud processing looks cheaper on a spreadsheet.
Data reduction value depends on whether the edge keeps the right information. A 95% reduction is useful only if summaries, features, or event windows preserve the diagnostic evidence that the cloud needs later. Reducing a vibration stream to fast Fourier transform (FFT) peaks may be correct for bearing monitoring, but reducing it to a single average can destroy the fault signature. The cost model must therefore pair each reduction rule with the decision it still supports.