Manu's Vault

Fallacy Bandwidth Is Infinite

3 min readStatus:Seedling

Core Idea

“Bandwidth is infinite” is the third of the Fallacies of Distributed Computing—the false assumption that network capacity is unlimited and you can transfer any amount of data without considering throughput constraints. In reality, bandwidth is finite, expensive, and often becomes a bottleneck when distributed systems transfer large payloads, stream data, or handle high-frequency communication between services.

What Is the “Bandwidth Is Infinite” Fallacy?

The fallacy assumes network connections can transmit unlimited data without capacity constraints, leading architects to freely pass large objects, transfer entire datasets between services, or implement chatty protocols without budgeting for cumulative bandwidth consumption.

Bandwidth varies dramatically by infrastructure:

  • Within a data center: 1–10 Gbps
  • Between data centers or cloud regions: 100 Mbps–1 Gbps
  • Internet/mobile connections: 5 Mbps–1 Gbps

The fallacy becomes critical at scale. A microservices architecture passing full domain objects instead of minimal DTOs will saturate bandwidth as call volumes grow — a 5 KB Customer object fetched for 1,000 orders per second consumes 40 Mbps from a single data flow. Multiply this across dozens of services and the network becomes the bottleneck, causing congestion, increased latency, and timeouts even when CPU and memory are healthy.

Bandwidth constraints also compound the latency fallacy: large payloads not only consume capacity but take longer to transmit. A 1 MB response over a 10 Mbps link adds 800ms of transfer time on top of network round-trip time.

Addressing this fallacy requires deliberate data transfer strategies:

  • Use minimal DTOs containing only required fields, not entire domain objects
  • Apply compression to reduce payload sizes
  • Cache frequently accessed data locally to avoid repeated transfers
  • Use pagination and lazy loading for large datasets
  • Design asynchronous, message-based communication to smooth bandwidth usage over time

Why This Matters

Bandwidth exhaustion creates performance bottlenecks that CPU or memory scaling cannot resolve — it is a fundamentally different resource. Cloud providers also charge for data transfer: egress fees, inter-region traffic, and cross-availability-zone traffic accumulate quickly in chatty architectures, making bandwidth a direct operational cost driver.

Distributed architectures must carefully manage what data crosses service boundaries and how often. For domains processing media, analytics, or large datasets, bandwidth is a primary operational characteristic that shapes the entire architecture — often requiring CDNs, data pre-positioning, or accepted latency trade-offs to stay within capacity limits.

Sources

  • Richards, Mark and Neal Ford (2020). Fundamentals of Software Architecture: An Engineering Approach. O’Reilly Media. ISBN: 978-1-492-04345-4.

  • Deutsch, Peter (1994-1997). “The Eight Fallacies of Distributed Computing.” Originally articulated at Sun Microsystems.

    • Third fallacy in the original list
    • Identified through observing repeated bandwidth exhaustion in distributed systems
    • Widely referenced in distributed systems literature

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.

Graph View

Backlinks