Debate: Edge vs. Cloud Processing Placement
Debate: Edge vs. Cloud Processing Placement
Debate: Edge vs. Cloud Processing Placement
This scenario is drawn from a manufacturing predictive-maintenance deployment and is meant to be worked through as a design-decision exercise.
Edge vs Cloud Processing
Keep One Urgent Decision Local
Picture a cold-room alarm that reaches the cloud after the safe response time has passed. Its audit history may travel later, but the urgent action cannot wait for an uncertain path.
Bandwidth means how much data a path can carry in a given time. Latency means the delay from an event to the response that depends on it.
Run the same event locally and through the cloud, then slow and disconnect the link. Keep event and action times, bandwidth use, latency, decision, missed deadline, buffered history, and recovery order.
This comparison covers one workload and failure set, not a universal placement rule. The prompt below asks which responsibilities belong near the device and which can move upstream.
Scenario: A manufacturing plant monitors 1,000 machines with vibration sensors (1kHz sampling). Goal: Predict failures before they happen.
Question: Where should the ML inference run?
Position A: Edge processing - Lower latency for real-time alerts - Bandwidth savings - Works during network outages
Position B: Cloud processing - More powerful models - Centralized model updates - Cross-plant pattern detection
Your Task: Each person picks a position and must defend it for 3 minutes. Then switch sides.