Editing Shared-nothing architecture

{{Short description|Type of  distributed computing architecture}}
A '''shared-nothing architecture''' ('''SN''') is a [[distributed computing]] [[Software architecture|architecture]] in which each update request is satisfied by a single node (processor/memory/storage unit) in a [[computer cluster]]. The intent is to eliminate contention among nodes. Nodes do not share (independently access) the same memory or storage. 

One alternative architecture is shared everything, in which requests are satisfied by arbitrary combinations of nodes. This may introduce contention, as multiple nodes may seek to update the same data at the same time. It also contrasts with [[Shared-disk architecture|shared-disk]] and [[Shared-memory architecture|shared-memory]] architectures. 

SN eliminates [[single point of failure|single points of failure]], allowing the overall system to continue operating despite failures in individual nodes and allowing individual nodes to upgrade hardware or software without a system-wide shutdown.<ref>{{cite web
 |url = https://blog.netapp.com/blogs/the-advantages-of-a-shared-nothing-architecture-for-truly-non-disruptive-upgrades/
 |title = The Advantages of a Shared Nothing Architecture for Truly Non-Disruptive Upgrades
 |last = Wright
 |first = Dave
 |publisher = netapp.com
 |date = 2014-09-17
 |access-date = 2019-10-31}}
 </ref>

A SN system can scale simply by adding nodes, since no central resource bottlenecks the system.<ref>{{cite web
 | last = Blankenhorn
 | first = Dana
 | title = Shared nothing coming to open source
 | publisher = ZDNet
 | date = February 27, 2006
 | url = http://www.zdnet.com/blog/open-source/shared-nothing-coming-to-open-source/580
 | archive-url = https://web.archive.org/web/20121004020313/http://www.zdnet.com/blog/open-source/shared-nothing-coming-to-open-source/580
 | url-status = dead
 | archive-date = October 4, 2012
 | access-date = June 21, 2012}}</ref> In databases, a term for the part of a database on a single node is a ''[[Shard (database architecture)|shard]]''. A SN system typically partitions its data among many nodes. A refinement is to replicate commonly used but infrequently modified data across many nodes, allowing more requests to be resolved on a single node.

== History ==
[[Michael Stonebraker]] at the [[University of California, Berkeley]] used the term in a 1986 database paper.<ref>{{cite journal |url=http://db.cs.berkeley.edu/papers/hpts85-nothing.pdf |title=The Case for Shared Nothing Architecture |author=Michael Stonebraker |journal=Database Engineering |volume=9 |number=1 |year=1986}}</ref> [[Teradata]] delivered the first SN database system in 1983.<ref>{{cite web|url=http://www.teradata.com/t/history/|title=Teradata History|publisher=Teradata.com|access-date=2013-06-16}}</ref> [[Tandem Computers]] [[NonStop (server computers)|NonStop]] systems, a shared-nothing implementation of hardware and software was released to market in 1976.<ref>{{Cite journal |date=Winter 1986 |title="Tandem History: An Introduction" |journal=Center Magazine: A Newsletter for Tandem Employees |volume=6 |issue=1}}</ref><ref>{{Cite web |title=History of TANDEM COMPUTERS, INC. – FundingUniverse |url=http://www.fundinguniverse.com/company-histories/tandem-computers-inc-history/ |access-date=2023-03-01 |website=www.fundinguniverse.com}}</ref> Tandem Computers later released [[NonStop SQL]], a shared-nothing relational database, in 1984.<ref>{{Cite web |url=http://www.hpl.hp.com/techreports/tandem/TR-87.4.pdf |title=NonStop SQL, A Distributed, High-Performance, High-Availability Implementation of SQL, Tandem Technical Report TR-87.4 |access-date=2012-10-11 |archive-date=2012-03-16 |archive-url=https://web.archive.org/web/20120316071651/http://www.hpl.hp.com/techreports/tandem/TR-87.4.pdf |url-status=dead }}</ref>

== Applications ==
Shared-nothing is popular for [[web development]].

Shared-nothing architectures are prevalent for [[data warehousing]] applications, although requests that require data from multiple nodes can dramatically reduce throughput.<ref>{{Cite web|url=http://db.csail.mit.edu/madden/high_perf.pdf|title=Article on Shared Nothing from the point of view of a Shared Nothing Vendor}}</ref>

==See also==
{{columns-list|
*[[NonStop_(server_computers)]]
*[[Teradata]]
*[[Oracle RAC]] (Shared Everything)
*[[Byzantine fault tolerance]]
*[[Distributed hash table]] (DHT)
*[[Exasol]]
*[[Greenplum]]
*[[Grid computing]]
*[[InfiniDB]]
*[[MySQL Cluster]]
*[[Openstack]]
*[[ScyllaDB]]
*[[DragonFlyDB]]
*[[Vertica]]
*[[Database scalability]]
*[[Gluster#GlusterFS|GlusterFS]]}}

==References==
{{Reflist}}

[[Category:Data partitioning]]
[[Category:Distributed computing architecture]]