imported>IvanStepaniuk: /* See also */ Update article link after page move

2025-03-21T12:30:03Z

See also: Update article link after page move

New page

{{Short description|False assumptions programmers make who are new to distributed computing}}
The '''fallacies of distributed computing''' are a set of assertions made by [[L Peter Deutsch]] and others at [[Sun Microsystems]] describing false assumptions that [[programmer]]s new to [[Distributed computing|distributed]] [[Application software|applications]] invariably make. 

==The fallacies==
The originally listed [[fallacy|fallacies]] are<ref name="8-Fallacies">{{cite web |last=Wilson |first=Gareth |date=2015-02-06 |title=The Eight Fallacies of Distributed Computing - Tech Talk |url=http://blog.fogcreek.com/eight-fallacies-of-distributed-computing-tech-talk/ |url-status=dead |archive-url=https://web.archive.org/web/20171107014323/http://blog.fogcreek.com/eight-fallacies-of-distributed-computing-tech-talk/ |archive-date=2017-11-07 |access-date=2017-06-18 |quote=The Eight Fallacies are something that I heard about at a Java One conference a long time ago by a guy named James Gosling. He attributed them to someone named Peter Deutsch and basically a bunch of guys at Sun had come up with a list of these fallacies.}}</ref>

# The [[Computer network|network]] is reliable;
# [[Latency (engineering)|Latency]] is zero;
# [[Throughput|Bandwidth]] is infinite;
# The network is [[Computer security|secure]];
# [[Network topology|Topology]] doesn't change;
# There is one [[Network administrator|administrator]];
# Transport cost is zero;
# The network is homogeneous;

==The effects of the fallacies==
# 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.
# 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.
# Ignorance of bandwidth limits on the part of traffic senders can result in bottlenecks.
# Complacency regarding network security results in being blindsided by malicious users and programs that continually adapt to security measures.
# Changes in [[network topology]] can have effects on both bandwidth and latency issues, and therefore can have similar problems.
# Multiple administrators, as with [[Subnetwork|subnets]] for rival companies, may institute conflicting policies of which senders of network traffic must be aware in order to complete their desired paths.
# 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.
# 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 originated at [[Sun Microsystems]]. [[L. Peter Deutsch]], one of the original Sun "[[Fellow]]s", first created a list of seven fallacies in 1994; incorporating four fallacies [[Bill Joy]] and Dave Lyon had already identified in "The Fallacies of Networked Computing".<ref name="Fallacies-10-years-after">{{cite web |last=Van Den Hoogen |first=Ingrid |date=2004-01-08 |title=Deutsch's Fallacies, 10 Years After |url=http://java.sys-con.com/read/38665.htm |url-status=dead |archive-url=https://web.archive.org/web/20070811082651/http://java.sys-con.com/read/38665.htm |archive-date=2007-08-11 |access-date=2005-12-03}}</ref> Around 1997, [[James Gosling]], another Sun Fellow and the inventor of [[Java (programming language)|Java]], added the eighth fallacy.<ref name="Fallacies-10-years-after" />

In an episode of "Software Engineering Radio" <ref>{{cite AV media |date=2021-07-27 |title=L. Peter Deutsch on the Fallacies of Distributed Computing |url=https://se-radio.net/2021/07/episode-470-l-peter-deutsch-on-the-fallacies-of-distributed-computing/ |time=57:10}}</ref> Peter Deutsch added a ninth fallacy: "It's really an expansion of number 4. It extends beyond the boundaries of the physical network. ... The party you are communicating with is trustworthy."

Later in 2020, Mark Richards and Neal Ford expanded upon the original "Fallacies of Distributed Computing" by introducing three additional fallacies to address contemporary challenges in distributed systems: <ref>{{Cite book |last=Richards |first=Mark |title=Fundamentals of Software Architecture: An Engineering Approach |publisher=O'Reilly Media |isbn=978-1492043454}}</ref>

* Versioning is simple
* Compensating updates always work
* Observability is optional

==See also==
* [[CAP theorem]]
* [[PACELC design principle]]
* [[Distributed computing]]
* [[Microservices#Criticism_and_concerns|Fine ''vs'' coarse grained SOA]]

==References==
<references/>

==External links==
* {{Cite web |last=Deutsch |first=Peter |url=https://nighthacks.com/jag/res/Fallacies.html |title=The Eight Fallacies of Distributed Computing |access-date=2024-07-24 |website=nighthacks.com}}
* {{Cite web |last=Rotem-Gal-Oz |first=Arnon |date=January 2008 |url=https://www.researchgate.net/publication/322500050_Fallacies_of_Distributed_Computing_Explained |title=Fallacies of Distributed Computing Explained |access-date=2024-07-24 |via=[[ResearchGate]]}}

[[Category:Distributed computing architecture]]
[[Category:Distributed computing problems]]

Fallacies of distributed computing - Revision history

imported>IvanStepaniuk: /* See also */ Update article link after page move