Fallacy Transport Cost Is Zero

Core Idea

“Transport cost is zero” is the seventh of the Fallacies of Distributed Computing—the false assumption that moving data across the network is free. In reality, network transport imposes both direct financial costs (bandwidth fees, infrastructure) and indirect costs (latency overhead, serialization/deserialization CPU cycles, increased operational complexity). Ignoring transport costs leads to architectures that make inefficient trade-offs between local computation and remote data access.

What Is the “Transport Cost Is Zero” Fallacy?

The “transport cost is zero” fallacy assumes that network communication is a cost-free operation that can be used liberally without economic or computational consequence. In practice, transport always costs something—whether measured in dollars, CPU cycles, latency, or energy.

Direct financial costs are easy to overlook at design time. Cloud providers charge for:

• Data egress (leaving their network): ~$0.09/GB on AWS
• Inter-region transfers: $0.01–0.02/GB
• Cross-availability-zone traffic

A microservices system transferring 10 GB/day between regions accumulates $100–200/month in pure bandwidth costs before any compute or storage. At terabyte-scale, transport costs can exceed compute costs.

Indirect computational costs are incurred on every call. Serializing data into transferable formats (JSON, Protocol Buffers, Avro), transmitting the bytes, and deserializing on the receiving end all consume CPU proportional to data size and complexity. A microservice making hundreds of external calls per request may spend more CPU on serialization than on business logic. This overhead doesn’t exist in monolithic architectures, where in-process calls pass object references directly without marshaling.

The fallacy becomes problematic when systems choose remote calls over local computation without cost analysis. A recommendation engine that could cache user preference data locally but instead fetches it from a remote service on every request pays network latency, bandwidth, serialization overhead, and availability dependencies—all potentially avoidable if the data changes infrequently.

Transport costs also interact with the bandwidth fallacy: chatty protocols with many small requests consume bandwidth inefficiently, adding per-request protocol overhead (HTTP headers, TCP/IP framing, TLS amortization). Consolidating requests into fewer, larger calls reduces both bandwidth consumption and per-request overhead.

Addressing this fallacy requires cost-aware design:

• Analyze whether distributing a service justifies ongoing transport costs
• Cache to minimize repeated remote data fetches
• Batch operations to amortize serialization and protocol overhead
• Choose efficient serialization formats — binary protocols (gRPC/Protocol Buffers) cost less than verbose JSON
• Co-locate frequently communicating services to avoid inter-region charges

Why This Matters

Organizations often discover transport costs late, after deploying distributed architectures that generate unexpected cloud bills. A microservices system delivering excellent scalability might incur $10,000/month in cross-region bandwidth charges—a cost that must be weighed against architectural benefits and should inform architecture style selection from the start.

Monolithic architectures eliminate transport costs by keeping communication in-process, but sacrifice independent scalability and deployment flexibility. Distributed architectures pay transport costs for those benefits. The optimal choice depends on whether the operational flexibility justifies the ongoing expense.

Related Concepts

• Fallacies-of-Distributed-Computing — The complete set of eight fallacies this belongs to
• Fallacy-Bandwidth-Is-Infinite — Related fallacy about unlimited bandwidth; transport cost makes bandwidth consumption expensive
• Fallacy-Latency-Is-Zero — Related fallacy about network delay; transport cost includes latency overhead
• Monolithic-vs-Distributed-Architectures — The architectural decision this fallacy significantly impacts
• Operational-Characteristics — Cost, performance, and energy efficiency are affected by transport costs
• Trade-Offs-and-Least-Worst-Architecture — Transport costs exemplify architectural trade-offs between distribution and cost
• Architecture-Style-Selection-Framework — Transport costs should inform architecture style decisions
• Microservices-Architecture-Style — Style that incurs significant transport costs; requires careful management
• Architecturally-Significant-Decisions — Transport costs can make technology choices architecturally significant

Sources

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

  • Chapter 9: Foundations
  • Discusses the Fallacies of Distributed Computing and their architectural implications
  • Available: https://www.oreilly.com/library/view/fundamentals-of-software/9781492043447/

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

  • Seventh fallacy in the original list
  • Identified through observing hidden costs in distributed system design
  • 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.