335  Edge and Fog Computing: Interactive Simulator

335.1 Learning Objectives

By the end of this chapter, you will be able to:

  • Visualize latency trade-offs: See how data size, complexity, and distance affect processing time
  • Compare tier costs: Understand bandwidth cost implications of edge, fog, and cloud
  • Apply real-world scenarios: Match common IoT applications to appropriate computing tiers
  • Make informed decisions: Choose the right architecture based on latency and cost requirements

335.2 Interactive: Edge-Fog-Cloud Latency Simulator

Explore how data size, processing complexity, network bandwidth, and distance affect total latency and bandwidth costs across the three-tier computing hierarchy. This simulator helps you understand when to use edge, fog, or cloud processing based on your application’s real-time requirements.

335.3 How to Use This Simulator

  1. Select a reference scenario from the dropdown to see recommended values for typical IoT use cases
  2. Adjust data size (1-1000 KB) to model your data payload
  3. Set network bandwidth (1-1000 Mbps) to model your network capacity
  4. Change distance to cloud (10-5000 km) to understand propagation delay impact
  5. Modify processing complexity to understand compute trade-offs (edge struggles with “Very High”, cloud excels)
  6. Set latency requirement to see which tiers meet your application’s real-time needs
  7. Adjust requests per day (1-86,400) to calculate monthly bandwidth costs accurately

335.4 Real-World Examples

Scenario Data Complexity Distance Latency Req Best Tier
Autonomous Car 50 KB Very High 50 km 10 ms Edge
Smart Meter 1 KB Low 2000 km 500 ms Cloud
Video Analytics 500 KB High 100 km 50 ms Fog
Industrial Sensor 10 KB Medium 200 km 20 ms Fog
Wearable Health 5 KB Low 1000 km 200 ms Fog/Cloud

335.5 Key Takeaways

  • Autonomous vehicles demonstrate why edge is mandatory for safety-critical applications: a 200ms cloud round-trip means the car travels 5+ meters before reacting
  • Smart meters show that low-data, latency-tolerant applications are perfect for cloud: centralized analytics across millions of devices
  • Video analytics proves fog computing’s sweet spot: local AI inference reduces bandwidth by 95% while meeting real-time requirements
  • Cost matters: Compare monthly bandwidth costs between tiers - edge processing can save thousands of dollars per month for high-volume IoT deployments
TipOptimize Data Placement Strategy

Don’t blindly process everything at the edge or everything in the cloud. Use a tiered decision framework: process time-critical decisions (<10ms requirement) at edge devices, aggregate and filter data at fog layer (reduces bandwidth by 90-99%), send only insights or anomalies to cloud for long-term storage and cross-site analytics. Example: A video surveillance system should detect motion at the camera (edge), perform object recognition at the fog gateway, and send only identified security events to cloud - not raw 24/7 video streams. This reduces a 1TB/day camera load to just 1GB/day in cloud storage costs.

335.6 What’s Next?

Now that you’ve explored the trade-offs interactively, see how these principles apply in real-world use cases.

Continue to Use Cases –>