imported>Kasriski at 06:47, 19 March 2026

2026-03-19T06:47:29Z

← Previous revision		Revision as of 06:47, 19 March 2026
Line 4:		Line 4:
	'''Distributed computing''' is a field of [[computer science]] that studies '''distributed systems''', defined as [[computer system]]s whose inter-communicating components are located on different [[computer network\|networked computers]].<ref name="tanenbaum">{{cite book \|author1=Tanenbaum, Andrew S. \|author2=Steen, Maarten van \|title=Distributed systems: principles and paradigms \|publisher=Pearson Prentice Hall \|location=Upper Saddle River, NJ \|year=2002 \|isbn=0-13-088893-1 \|url=https://www.distributed-systems.net/index.php/books/ds3/ \|access-date=2020-08-28 \|archive-date=2020-08-12 \|archive-url=https://web.archive.org/web/20200812174339/https://www.distributed-systems.net/index.php/books/ds3/ \|url-status=live }}</ref><ref name="Distributed Programs 2010 pp. 373–406">{{cite book \| title=Texts in Computer Science \| chapter=Distributed Programs \| publisher=Springer London \| publication-place=London \| year=2010 \| isbn=978-1-84882-744-8 \| issn=1868-0941 \| doi=10.1007/978-1-84882-745-5_11 \| pages=373–406 \| quote=Systems consist of a number of physically distributed components that work independently using their private storage, but also communicate from time to time by explicit message passing. Such systems are called distributed systems.}}</ref>		'''Distributed computing''' is a field of [[computer science]] that studies '''distributed systems''', defined as [[computer system]]s whose inter-communicating components are located on different [[computer network\|networked computers]].<ref name="tanenbaum">{{cite book \|author1=Tanenbaum, Andrew S. \|author2=Steen, Maarten van \|title=Distributed systems: principles and paradigms \|publisher=Pearson Prentice Hall \|location=Upper Saddle River, NJ \|year=2002 \|isbn=0-13-088893-1 \|url=https://www.distributed-systems.net/index.php/books/ds3/ \|access-date=2020-08-28 \|archive-date=2020-08-12 \|archive-url=https://web.archive.org/web/20200812174339/https://www.distributed-systems.net/index.php/books/ds3/ \|url-status=live }}</ref><ref name="Distributed Programs 2010 pp. 373–406">{{cite book \| title=Texts in Computer Science \| chapter=Distributed Programs \| publisher=Springer London \| publication-place=London \| year=2010 \| isbn=978-1-84882-744-8 \| issn=1868-0941 \| doi=10.1007/978-1-84882-745-5_11 \| pages=373–406 \| quote=Systems consist of a number of physically distributed components that work independently using their private storage, but also communicate from time to time by explicit message passing. Such systems are called distributed systems.}}</ref>

	The components of a distributed system communicate and coordinate their actions by [[message passing\|passing messages]] to one another in order to achieve a common goal. Three challenges of distributed systems are: maintaining [[Concurrency (computer science)\|concurrency]] of components, overcoming the [[clock synchronization\|lack of a global clock]], and managing the independent failure of components.<ref name="tanenbaum" /> When a component of one system fails, the entire system does not fail.{{sfn\|Dusseau\|Dusseau\|2016\|p=1–2}} Examples of distributed systems vary from [[service-oriented architecture\|SOA-based systems]] to [[microservices]] to [[massively multiplayer online game]]s to [[peer-to-peer\|peer-to-peer applications]]. Distributed systems cost more than monolithic architectures, primarily due to increased needs for additional hardware, servers, gateways, firewalls, new subnets, proxies, and so on.<ref>{{Cite book \|last=Ford \|first=Neal \|title=Fundamentals of Software Architecture: An Engineering Approach \|date=March 3, 2020 \|publisher=O'Reilly Media \|isbn=978-1-4920-4345-4 \|edition=1st \|pages=146–147}}</ref> Distributed systems can also suffer from [[fallacies of distributed computing]]. Conversely, a well-designed distributed system is more scalable, more durable, more changeable, and more fine-tuned than a [[monolithic application]] deployed on a single machine.<ref>{{Cite book \|title=Monolith to Microservices Evolutionary Patterns to Transform Your Monolith \|publisher=O'Reilly Media \|isbn=978-1-4920-4781-0}}</ref> According to Marc Brooker: "a system is scalable in the range where [[marginal cost]] of additional workload is nearly constant." [[Serverless computing\|Serverless]] technologies fit this definition but the total cost of ownership, and not just the ~~infra~~ cost must be considered.<ref>{{Cite book \|title=Building Serverless Applications on Knative \|publisher=O'Reilly Media \|isbn=978-1-0981-4204-9}}</ref>		The components of a distributed system communicate and coordinate their actions by [[message passing\|passing messages]] to one another in order to achieve a common goal. Three challenges of distributed systems are: maintaining [[Concurrency (computer science)\|concurrency]] of components, overcoming the [[clock synchronization\|lack of a global clock]], and managing the independent failure of components.<ref name="tanenbaum" /> When a component of one system fails, the entire system does not fail.{{sfn\|Dusseau\|Dusseau\|2016\|p=1–2}} Examples of distributed systems vary from [[service-oriented architecture\|SOA-based systems]] to [[microservices]] to [[massively multiplayer online game]]s to [[peer-to-peer\|peer-to-peer applications]]. Distributed systems cost more than monolithic architectures, primarily due to increased needs for additional hardware, servers, gateways, firewalls, new subnets, proxies, and so on.<ref>{{Cite book \|last=Ford \|first=Neal \|title=Fundamentals of Software Architecture: An Engineering Approach \|date=March 3, 2020 \|publisher=O'Reilly Media \|isbn=978-1-4920-4345-4 \|edition=1st \|pages=146–147}}</ref> Distributed systems can also suffer from [[fallacies of distributed computing]]. Conversely, a well-designed distributed system is more scalable, more durable, more changeable, and more fine-tuned than a [[monolithic application]] deployed on a single machine.<ref>{{Cite book \|title=Monolith to Microservices Evolutionary Patterns to Transform Your Monolith \|publisher=O'Reilly Media \|isbn=978-1-4920-4781-0}}</ref> According to Marc Brooker: "a system is scalable in the range where [[marginal cost]] of additional workload is nearly constant." [[Serverless computing\|Serverless]] technologies fit this definition but the total cost of ownership, and not just the infrastructure cost must be considered.<ref>{{Cite book \|title=Building Serverless Applications on Knative \|publisher=O'Reilly Media \|isbn=978-1-0981-4204-9}}</ref>

	A [[computer program]] that runs within a distributed system is called a '''distributed program''',<ref name="Distributed Programs 2010 pp. 373–406 II">{{cite book \| title=Texts in Computer Science \| chapter=Distributed Programs \| publisher=Springer London \| publication-place=London \| year=2010 \| isbn=978-1-84882-744-8 \| issn=1868-0941 \| doi=10.1007/978-1-84882-745-5_11 \| pages=373–406 \| quote=Distributed programs are abstract descriptions of distributed systems. A distributed program consists of a collection of processes that work concurrently and communicate by explicit message passing. Each process can access a set of variables which are disjoint from the variables that can be changed by any other process.}}</ref> and ''distributed programming'' is the process of writing such programs.<ref>{{harvtxt\|Andrews\|2000}}. {{harvtxt\|Dolev\|2000}}. {{harvtxt\|Ghosh\|2007}}, p. 10.</ref> There are many types of implementations for the message-passing mechanism, including pure HTTP, [[remote procedure call\|RPC-like]] connectors, and [[message-oriented middleware\|message queues]].<ref>{{Cite journal\|last=Magnoni\|first=L.\|date=2015\|title=Modern Messaging for Distributed Sytems (sic)\|journal=Journal of Physics: Conference Series\|language=en\|volume=608\|issue=1\|article-number=012038\|doi=10.1088/1742-6596/608/1/012038\|issn=1742-6596\|doi-access=free\|bibcode=2015JPhCS.608a2038M }}</ref>		A [[computer program]] that runs within a distributed system is called a '''distributed program''',<ref name="Distributed Programs 2010 pp. 373–406 II">{{cite book \| title=Texts in Computer Science \| chapter=Distributed Programs \| publisher=Springer London \| publication-place=London \| year=2010 \| isbn=978-1-84882-744-8 \| issn=1868-0941 \| doi=10.1007/978-1-84882-745-5_11 \| pages=373–406 \| quote=Distributed programs are abstract descriptions of distributed systems. A distributed program consists of a collection of processes that work concurrently and communicate by explicit message passing. Each process can access a set of variables which are disjoint from the variables that can be changed by any other process.}}</ref> and ''distributed programming'' is the process of writing such programs.<ref>{{harvtxt\|Andrews\|2000}}. {{harvtxt\|Dolev\|2000}}. {{harvtxt\|Ghosh\|2007}}, p. 10.</ref> There are many types of implementations for the message-passing mechanism, including pure HTTP, [[remote procedure call\|RPC-like]] connectors, and [[message-oriented middleware\|message queues]].<ref>{{Cite journal\|last=Magnoni\|first=L.\|date=2015\|title=Modern Messaging for Distributed Sytems (sic)\|journal=Journal of Physics: Conference Series\|language=en\|volume=608\|issue=1\|article-number=012038\|doi=10.1088/1742-6596/608/1/012038\|issn=1742-6596\|doi-access=free\|bibcode=2015JPhCS.608a2038M }}</ref>
Line 33:		Line 33:
	* [[Microservices]]		* [[Microservices]]
	* [[Event driven architecture]]		* [[Event driven architecture]]
			* [[Client–server model\|Client–server architecture]]
			* [[Service-oriented architecture\|Service-oriented architecture (SOA)]]
			* [[Publish–subscribe pattern]]
			* [[Peer-to-peer\|Peer-to-peer (P2P)]]

	== Events vs. Messages ==		== Events vs. Messages ==
Line 219:		Line 223:
	{{Div col\|colwidth=20em}}		{{Div col\|colwidth=20em}}
	* {{annotated link\|Actor model}}		* {{annotated link\|Actor model}}
	* {{annotated link\|AppScale}}
	* {{annotated link\|BOINC}}
	* {{annotated link\|Code mobility}}		* {{annotated link\|Code mobility}}
	* {{annotated link\|Dataflow programming}}		* {{annotated link\|Dataflow programming}}
Line 227:		Line 229:
	* {{annotated link\|Distributed algorithmic mechanism design}}		* {{annotated link\|Distributed algorithmic mechanism design}}
	* {{annotated link\|Distributed cache}}		* {{annotated link\|Distributed cache}}
	* {{annotated link\|Distributed GIS}}
	* {{annotated link\|Distributed networking}}		* {{annotated link\|Distributed networking}}
	* {{annotated link\|Distributed operating system}}		* {{annotated link\|Distributed operating system}}
Line 235:		Line 236:
	* {{annotated link\|Flat neighborhood network}}		* {{annotated link\|Flat neighborhood network}}
	* {{annotated link\|Fog computing}}		* {{annotated link\|Fog computing}}
	* {{annotated link\|Folding@home}}
	* {{annotated link\|Grid computing}}		* {{annotated link\|Grid computing}}
	* {{annotated link\|Inferno (operating system)\|Inferno}}
	* {{annotated link\|Internet GIS}}		* {{annotated link\|Internet GIS}}
	* {{annotated link\|Jungle computing}}		* {{annotated link\|Jungle computing}}
Line 245:		Line 244:
	* {{annotated link\|List of volunteer computing projects}}		* {{annotated link\|List of volunteer computing projects}}
	* {{annotated link\|Model checking}}		* {{annotated link\|Model checking}}
	* {{annotated link\|OpenHarmony}}
	* {{annotated link\|HarmonyOS}}
	* {{annotated link\|Parallel distributed processing}}		* {{annotated link\|Parallel distributed processing}}
	* {{annotated link\|Parallel programming model}}		* {{annotated link\|Parallel programming model}}
	* {{annotated link\|Plan 9 from Bell Labs}}
	* {{annotated link\|Shared nothing architecture}}		* {{annotated link\|Shared nothing architecture}}
	* {{annotated link\|Web GIS}}
	{{div col end}}		{{div col end}}

~2026-2699: /* External links */

2026-01-01T01:44:58Z

External links

← Previous revision		Revision as of 01:44, 1 January 2026
Line 472:		Line 472:

	{{Parallel computing}}		{{Parallel computing}}
			{{Programming paradigms navbox}}
	{{Authority control}}		{{Authority control}}

	{{DEFAULTSORT:Distributed Computing}}		{{DEFAULTSORT:Distributed Computing}}
	[[Category:Distributed computing\| ]]		[[Category:Distributed computing\| ]]

~2025-33045-91: Made the Heading of this section a bit more clear. (Minor Edit)

2025-11-12T15:43:29Z

Made the Heading of this section a bit more clear. (Minor Edit)

Show changes

imported>Citation bot: Altered pages. Add: publisher, date, bibcode, authors 1-2. Removed parameters. Formatted dashes. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Dominic3203 | Linked from User:LinguisticMystic/cs/outline | #UCB_webform_linked 571/2277

2025-04-16T18:52:01Z

Altered pages. Add: publisher, date, bibcode, authors 1-2. Removed parameters. Formatted dashes. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Dominic3203 | Linked from User:LinguisticMystic/cs/outline | #UCB_webform_linked 571/2277

Show changes

← Previous revision		Revision as of 06:47, 19 March 2026
Line 4:		Line 4:
	'''Distributed computing''' is a field of [[computer science]] that studies '''distributed systems''', defined as [[computer system]]s whose inter-communicating components are located on different [[computer network\|networked computers]].<ref name="tanenbaum">{{cite book \|author1=Tanenbaum, Andrew S. \|author2=Steen, Maarten van \|title=Distributed systems: principles and paradigms \|publisher=Pearson Prentice Hall \|location=Upper Saddle River, NJ \|year=2002 \|isbn=0-13-088893-1 \|url=https://www.distributed-systems.net/index.php/books/ds3/ \|access-date=2020-08-28 \|archive-date=2020-08-12 \|archive-url=https://web.archive.org/web/20200812174339/https://www.distributed-systems.net/index.php/books/ds3/ \|url-status=live }}</ref><ref name="Distributed Programs 2010 pp. 373–406">{{cite book \| title=Texts in Computer Science \| chapter=Distributed Programs \| publisher=Springer London \| publication-place=London \| year=2010 \| isbn=978-1-84882-744-8 \| issn=1868-0941 \| doi=10.1007/978-1-84882-745-5_11 \| pages=373–406 \| quote=Systems consist of a number of physically distributed components that work independently using their private storage, but also communicate from time to time by explicit message passing. Such systems are called distributed systems.}}</ref>		'''Distributed computing''' is a field of [[computer science]] that studies '''distributed systems''', defined as [[computer system]]s whose inter-communicating components are located on different [[computer network\|networked computers]].<ref name="tanenbaum">{{cite book \|author1=Tanenbaum, Andrew S. \|author2=Steen, Maarten van \|title=Distributed systems: principles and paradigms \|publisher=Pearson Prentice Hall \|location=Upper Saddle River, NJ \|year=2002 \|isbn=0-13-088893-1 \|url=https://www.distributed-systems.net/index.php/books/ds3/ \|access-date=2020-08-28 \|archive-date=2020-08-12 \|archive-url=https://web.archive.org/web/20200812174339/https://www.distributed-systems.net/index.php/books/ds3/ \|url-status=live }}</ref><ref name="Distributed Programs 2010 pp. 373–406">{{cite book \| title=Texts in Computer Science \| chapter=Distributed Programs \| publisher=Springer London \| publication-place=London \| year=2010 \| isbn=978-1-84882-744-8 \| issn=1868-0941 \| doi=10.1007/978-1-84882-745-5_11 \| pages=373–406 \| quote=Systems consist of a number of physically distributed components that work independently using their private storage, but also communicate from time to time by explicit message passing. Such systems are called distributed systems.}}</ref>

	The components of a distributed system communicate and coordinate their actions by [[message passing\|passing messages]] to one another in order to achieve a common goal. Three challenges of distributed systems are: maintaining [[Concurrency (computer science)\|concurrency]] of components, overcoming the [[clock synchronization\|lack of a global clock]], and managing the independent failure of components.<ref name="tanenbaum" /> When a component of one system fails, the entire system does not fail.{{sfn\|Dusseau\|Dusseau\|2016\|p=1–2}} Examples of distributed systems vary from [[service-oriented architecture\|SOA-based systems]] to [[microservices]] to [[massively multiplayer online game]]s to [[peer-to-peer\|peer-to-peer applications]]. Distributed systems cost more than monolithic architectures, primarily due to increased needs for additional hardware, servers, gateways, firewalls, new subnets, proxies, and so on.<ref>{{Cite book \|last=Ford \|first=Neal \|title=Fundamentals of Software Architecture: An Engineering Approach \|date=March 3, 2020 \|publisher=O'Reilly Media \|isbn=978-1-4920-4345-4 \|edition=1st \|pages=146–147}}</ref> Distributed systems can also suffer from [[fallacies of distributed computing]]. Conversely, a well-designed distributed system is more scalable, more durable, more changeable, and more fine-tuned than a [[monolithic application]] deployed on a single machine.<ref>{{Cite book \|title=Monolith to Microservices Evolutionary Patterns to Transform Your Monolith \|publisher=O'Reilly Media \|isbn=978-1-4920-4781-0}}</ref> According to Marc Brooker: "a system is scalable in the range where [[marginal cost]] of additional workload is nearly constant." [[Serverless computing\|Serverless]] technologies fit this definition but the total cost of ownership, and not just the ~~infra~~ cost must be considered.<ref>{{Cite book \|title=Building Serverless Applications on Knative \|publisher=O'Reilly Media \|isbn=978-1-0981-4204-9}}</ref>		The components of a distributed system communicate and coordinate their actions by [[message passing\|passing messages]] to one another in order to achieve a common goal. Three challenges of distributed systems are: maintaining [[Concurrency (computer science)\|concurrency]] of components, overcoming the [[clock synchronization\|lack of a global clock]], and managing the independent failure of components.<ref name="tanenbaum" /> When a component of one system fails, the entire system does not fail.{{sfn\|Dusseau\|Dusseau\|2016\|p=1–2}} Examples of distributed systems vary from [[service-oriented architecture\|SOA-based systems]] to [[microservices]] to [[massively multiplayer online game]]s to [[peer-to-peer\|peer-to-peer applications]]. Distributed systems cost more than monolithic architectures, primarily due to increased needs for additional hardware, servers, gateways, firewalls, new subnets, proxies, and so on.<ref>{{Cite book \|last=Ford \|first=Neal \|title=Fundamentals of Software Architecture: An Engineering Approach \|date=March 3, 2020 \|publisher=O'Reilly Media \|isbn=978-1-4920-4345-4 \|edition=1st \|pages=146–147}}</ref> Distributed systems can also suffer from [[fallacies of distributed computing]]. Conversely, a well-designed distributed system is more scalable, more durable, more changeable, and more fine-tuned than a [[monolithic application]] deployed on a single machine.<ref>{{Cite book \|title=Monolith to Microservices Evolutionary Patterns to Transform Your Monolith \|publisher=O'Reilly Media \|isbn=978-1-4920-4781-0}}</ref> According to Marc Brooker: "a system is scalable in the range where [[marginal cost]] of additional workload is nearly constant." [[Serverless computing\|Serverless]] technologies fit this definition but the total cost of ownership, and not just the infrastructure cost must be considered.<ref>{{Cite book \|title=Building Serverless Applications on Knative \|publisher=O'Reilly Media \|isbn=978-1-0981-4204-9}}</ref>

	A [[computer program]] that runs within a distributed system is called a '''distributed program''',<ref name="Distributed Programs 2010 pp. 373–406 II">{{cite book \| title=Texts in Computer Science \| chapter=Distributed Programs \| publisher=Springer London \| publication-place=London \| year=2010 \| isbn=978-1-84882-744-8 \| issn=1868-0941 \| doi=10.1007/978-1-84882-745-5_11 \| pages=373–406 \| quote=Distributed programs are abstract descriptions of distributed systems. A distributed program consists of a collection of processes that work concurrently and communicate by explicit message passing. Each process can access a set of variables which are disjoint from the variables that can be changed by any other process.}}</ref> and ''distributed programming'' is the process of writing such programs.<ref>{{harvtxt\|Andrews\|2000}}. {{harvtxt\|Dolev\|2000}}. {{harvtxt\|Ghosh\|2007}}, p. 10.</ref> There are many types of implementations for the message-passing mechanism, including pure HTTP, [[remote procedure call\|RPC-like]] connectors, and [[message-oriented middleware\|message queues]].<ref>{{Cite journal\|last=Magnoni\|first=L.\|date=2015\|title=Modern Messaging for Distributed Sytems (sic)\|journal=Journal of Physics: Conference Series\|language=en\|volume=608\|issue=1\|article-number=012038\|doi=10.1088/1742-6596/608/1/012038\|issn=1742-6596\|doi-access=free\|bibcode=2015JPhCS.608a2038M }}</ref>		A [[computer program]] that runs within a distributed system is called a '''distributed program''',<ref name="Distributed Programs 2010 pp. 373–406 II">{{cite book \| title=Texts in Computer Science \| chapter=Distributed Programs \| publisher=Springer London \| publication-place=London \| year=2010 \| isbn=978-1-84882-744-8 \| issn=1868-0941 \| doi=10.1007/978-1-84882-745-5_11 \| pages=373–406 \| quote=Distributed programs are abstract descriptions of distributed systems. A distributed program consists of a collection of processes that work concurrently and communicate by explicit message passing. Each process can access a set of variables which are disjoint from the variables that can be changed by any other process.}}</ref> and ''distributed programming'' is the process of writing such programs.<ref>{{harvtxt\|Andrews\|2000}}. {{harvtxt\|Dolev\|2000}}. {{harvtxt\|Ghosh\|2007}}, p. 10.</ref> There are many types of implementations for the message-passing mechanism, including pure HTTP, [[remote procedure call\|RPC-like]] connectors, and [[message-oriented middleware\|message queues]].<ref>{{Cite journal\|last=Magnoni\|first=L.\|date=2015\|title=Modern Messaging for Distributed Sytems (sic)\|journal=Journal of Physics: Conference Series\|language=en\|volume=608\|issue=1\|article-number=012038\|doi=10.1088/1742-6596/608/1/012038\|issn=1742-6596\|doi-access=free\|bibcode=2015JPhCS.608a2038M }}</ref>
Line 33:		Line 33:
	* [[Microservices]]		* [[Microservices]]
	* [[Event driven architecture]]		* [[Event driven architecture]]
			* [[Client–server model\|Client–server architecture]]
			* [[Service-oriented architecture\|Service-oriented architecture (SOA)]]
			* [[Publish–subscribe pattern]]
			* [[Peer-to-peer\|Peer-to-peer (P2P)]]

	== Events vs. Messages ==		== Events vs. Messages ==
Line 219:		Line 223:
	{{Div col\|colwidth=20em}}		{{Div col\|colwidth=20em}}
	* {{annotated link\|Actor model}}		* {{annotated link\|Actor model}}
	* {{annotated link\|AppScale}}
	* {{annotated link\|BOINC}}
	* {{annotated link\|Code mobility}}		* {{annotated link\|Code mobility}}
	* {{annotated link\|Dataflow programming}}		* {{annotated link\|Dataflow programming}}
Line 227:		Line 229:
	* {{annotated link\|Distributed algorithmic mechanism design}}		* {{annotated link\|Distributed algorithmic mechanism design}}
	* {{annotated link\|Distributed cache}}		* {{annotated link\|Distributed cache}}
	* {{annotated link\|Distributed GIS}}
	* {{annotated link\|Distributed networking}}		* {{annotated link\|Distributed networking}}
	* {{annotated link\|Distributed operating system}}		* {{annotated link\|Distributed operating system}}
Line 235:		Line 236:
	* {{annotated link\|Flat neighborhood network}}		* {{annotated link\|Flat neighborhood network}}
	* {{annotated link\|Fog computing}}		* {{annotated link\|Fog computing}}
	* {{annotated link\|Folding@home}}
	* {{annotated link\|Grid computing}}		* {{annotated link\|Grid computing}}
	* {{annotated link\|Inferno (operating system)\|Inferno}}
	* {{annotated link\|Internet GIS}}		* {{annotated link\|Internet GIS}}
	* {{annotated link\|Jungle computing}}		* {{annotated link\|Jungle computing}}
Line 245:		Line 244:
	* {{annotated link\|List of volunteer computing projects}}		* {{annotated link\|List of volunteer computing projects}}
	* {{annotated link\|Model checking}}		* {{annotated link\|Model checking}}
	* {{annotated link\|OpenHarmony}}
	* {{annotated link\|HarmonyOS}}
	* {{annotated link\|Parallel distributed processing}}		* {{annotated link\|Parallel distributed processing}}
	* {{annotated link\|Parallel programming model}}		* {{annotated link\|Parallel programming model}}
	* {{annotated link\|Plan 9 from Bell Labs}}
	* {{annotated link\|Shared nothing architecture}}		* {{annotated link\|Shared nothing architecture}}
	* {{annotated link\|Web GIS}}
	{{div col end}}		{{div col end}}

Distributed computing - Revision history

imported>Kasriski at 06:47, 19 March 2026

~2026-2699: /* External links */

~2025-33045-91: Made the Heading of this section a bit more clear. (Minor Edit)