Jump to content

Fallacies of distributed computing

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Netjeff (talk | contribs) at 23:35, 14 October 2016 (→See also: Added links to CAP and PACELC theorems). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The fallacies of distributed computing are a set of assertions made by L Peter Deutsch and others at Sun Microsystems describing false assumptions that programmers new to distributed applications invariably make. These result either in the failure of the system, a substantial reduction in system scope, or in large, unplanned expenses required to redesign the system to meet its original goals.[citation needed]

The fallacies

The fallacies are:[1]

  1. The network is reliable.
  2. Latency is zero.
  3. Bandwidth is infinite.
  4. The network is secure.
  5. Topology doesn't change.
  6. There is one administrator.
  7. Transport cost is zero.
  8. The network is homogeneous.

The effects of the fallacies

  1. Software applications are written with little error-handling on networking errors. During a network outage, such applications may stall or infinitely wait for an answer packet, permanently consuming memory or other resources. When the failed network becomes available, those applications may also fail to retry any stalled operations or require a (manual) restart.
  2. Ignorance of network latency, and of the packet loss it can cause, induces application- and transport-layer developers to allow unbounded traffic, greatly increasing dropped packets and wasting bandwidth.
  3. Ignorance of bandwidth limits on the part of traffic senders can result in bottlenecks over frequency-multiplexed media.
  4. Complacency regarding network security results in being blindsided by malicious users and programs that continually adapt to security measures.[2]
  5. Changes in network topology can have effects on both bandwidth and latency issues, and therefore similar problems.
  6. Multiple administrators, as with subnets for rival companies, may institute conflicting policies of which senders of network traffic must be aware in order to complete their desired paths.
  7. The "hidden" costs of building and maintaining a network or subnet are non-negligible and must consequently be noted in budgets to avoid vast shortfalls.
  8. If a system assumes a homogeneous network, then it can lead to the same problems that result from the first three fallacies.

History

The list of fallacies generally[clarification needed] came about at Sun Microsystems. L. Peter Deutsch, one of the original Sun "Fellows", is credited[by whom?] with penning the first seven fallacies in 1994; however, Bill Joy and Tom Lyon had already identified the first four as "The Fallacies of Networked Computing"[3] (the article claims "Dave Lyon", but this is a mistake). Around 1997, James Gosling, another Sun Fellow and the inventor of Java, added the eighth fallacy.[3]

See also

References

  1. ^ "The Eight Fallacies of Distributed Computing".
  2. ^ "Malware Defensive Techniques Will Evolve as Security Arms Race Continues".
  3. ^ a b "Deutsch's Fallacies, 10 Years After".


Stub icon

This computer networking article is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Fallacies_of_distributed_computing&oldid=744398126"