In the world of Fallacies of distributed computing, there are endless questions and debates that revolve around this topic. From its origins to its impact on today's society, Fallacies of distributed computing has been the subject of fascination and questioning. In this article, we will explore the different facets of Fallacies of distributed computing, analyzing its most relevant aspects and its influence in various areas. Through an interdisciplinary approach, we will seek to shed light on this topic, offering diverse and enriching perspectives that contribute to a broader and deeper understanding of Fallacies of 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 programmers new to distributed applications invariably make.
The originally listed fallacies are[1]
The list of fallacies originated at Sun Microsystems. L. Peter Deutsch, one of the original Sun "Fellows", 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".[2] Around 1997, James Gosling, another Sun Fellow and the inventor of Java, added the eighth fallacy.[2]
In an episode of "Software Engineering Radio" [3] 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: [4]
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.