Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Fallacies of distributed computing
open-in-new
<h2 id="the-fallacies">The fallacies</h2> <p>The originally listed <a href="/facts/Fallacy/IRVuLSef">fallacies</a> are<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> </p> <ol><li>The <a href="/facts/Computer_network/3w5RM99p">network</a> is reliable;</li> <li><a href="/facts/Latency_(engineering)/6Bjhn30H">Latency</a> is zero;</li> <li><a href="/facts/Throughput/6zAUsXqw">Bandwidth</a> is infinite;</li> <li>The network is <a href="/facts/Computer_security/7E5dIy7G">secure</a>;</li> <li><a href="/facts/Network_topology/rBYE0kke">Topology</a> doesn't change;</li> <li>There is one <a href="/facts/Network_administrator/UIwK6HTt">administrator</a>;</li> <li>Transport cost is zero;</li> <li>The network is homogeneous;</li></ol> <h2 id="the-effects-of-the-fallacies">The effects of the fallacies</h2> <ol><li>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.</li> <li>Ignorance of network latency, and of the <a href="/facts/Packet_loss/6fuIcFHk">packet loss</a> it can cause, induces application- and transport-layer developers to allow unbounded traffic, greatly increasing dropped packets and wasting bandwidth.</li> <li>Ignorance of bandwidth limits on the part of traffic senders can result in bottlenecks.</li> <li>Complacency regarding network security results in being blindsided by malicious users and programs that continually adapt to security measures.</li> <li>Changes in <a href="/facts/Network_topology/rBYE0kke">network topology</a> can have effects on both bandwidth and latency issues, and therefore can have similar problems.</li> <li>Multiple administrators, as with <a href="/facts/Subnetwork/s1rQsNDv">subnets</a> for rival companies, may institute conflicting policies of which senders of network traffic must be aware in order to complete their desired paths.</li> <li>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.</li> <li>If a system assumes a homogeneous network, then it can lead to the same problems that result from the first three fallacies.</li></ol> <h2 id="history">History</h2> <p>The list of fallacies originated at <a href="/facts/Sun_Microsystems/VJ9EzEFd">Sun Microsystems</a>. <a href="/facts/L._Peter_Deutsch/f4BmluYL">L. Peter Deutsch</a>, one of the original Sun "<a href="/facts/Fellow/DLThQbkq">Fellows</a>", first created a list of seven fallacies in 1994; incorporating four fallacies <a href="/facts/Bill_Joy/3I8ehVtu">Bill Joy</a> and Dave Lyon had already identified in "The Fallacies of Networked Computing".<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> Around 1997, <a href="/facts/James_Gosling/AIKS55X9">James Gosling</a>, another Sun Fellow and the inventor of <a href="/facts/Java_(programming_language)/9ScgFyAL">Java</a>, added the eighth fallacy.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> </p><p>In an episode of "Software Engineering Radio" <a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> 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." </p><p>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: <a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> </p> <ul><li>Versioning is simple</li> <li>Compensating updates always work</li> <li>Observability is optional</li></ul> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/CAP_theorem/qnxvcbLp">CAP theorem</a></li> <li><a href="/facts/PACELC_design_principle/TC0cVdgg">PACELC design principle</a></li> <li><a href="/facts/Distributed_computing/o5nyhqTF">Distributed computing</a></li> <li><a href="/facts/Microservices/1zGcNFSj">Fine <i>vs</i> coarse grained SOA</a></li></ul> <h2 id="external-links">External links</h2> <ul><li>Deutsch, Peter. <a href="https://nighthacks.com/jag/res/Fallacies.html">"The Eight Fallacies of Distributed Computing"</a>. <i>nighthacks.com</i>. Retrieved 2024-07-24.</li> <li>Rotem-Gal-Oz, Arnon (January 2008). <a href="https://www.researchgate.net/publication/322500050_Fallacies_of_Distributed_Computing_Explained">"Fallacies of Distributed Computing Explained"</a>. Retrieved 2024-07-24 – via <a href="/facts/ResearchGate/tyxv0zvV">ResearchGate</a>.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Wilson, Gareth (2015-02-06). "The Eight Fallacies of Distributed Computing - Tech Talk". Archived from the original on 2017-11-07. Retrieved 2017-06-18. 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. <a href="https://web.archive.org/web/20171107014323/http://blog.fogcreek.com/eight-fallacies-of-distributed-computing-tech-talk/" target="_blank">https://web.archive.org/web/20171107014323/http://blog.fogcreek.com/eight-fallacies-of-distributed-computing-tech-talk/</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Van Den Hoogen, Ingrid (2004-01-08). "Deutsch's Fallacies, 10 Years After". Archived from the original on 2007-08-11. Retrieved 2005-12-03. <a href="https://web.archive.org/web/20070811082651/http://java.sys-con.com/read/38665.htm" target="_blank">https://web.archive.org/web/20070811082651/http://java.sys-con.com/read/38665.htm</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Van Den Hoogen, Ingrid (2004-01-08). "Deutsch's Fallacies, 10 Years After". Archived from the original on 2007-08-11. Retrieved 2005-12-03. <a href="https://web.archive.org/web/20070811082651/http://java.sys-con.com/read/38665.htm" target="_blank">https://web.archive.org/web/20070811082651/http://java.sys-con.com/read/38665.htm</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>L. Peter Deutsch on the Fallacies of Distributed Computing. 2021-07-27. Event occurs at 57:10. <a href="https://se-radio.net/2021/07/episode-470-l-peter-deutsch-on-the-fallacies-of-distributed-computing/" target="_blank">https://se-radio.net/2021/07/episode-470-l-peter-deutsch-on-the-fallacies-of-distributed-computing/</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Richards, Mark. Fundamentals of Software Architecture: An Engineering Approach. O'Reilly Media. ISBN 978-1492043454. <a href="978-1492043454" target="_blank">978-1492043454</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> </ol>