Shared-nothing architecture

shared-nothingshared nothing architectureshared nothingShared nothing concurrent programming
A shared-nothing architecture (SN) is a distributed-computing architecture in which each node is independent and self-sufficient, and there is no single point of contention across the system.wikipedia
81 Related Articles

Tandem Computers

TandemHP NonStop (Tandem) serversTandem Himalaya
Tandem Computers officially released NonStop SQL, a shared nothing database, in 1984.
Besides handling failures well, this "shared-nothing" messaging system design also scales extremely well to the largest commercial workloads.

Database

database management systemdatabasesdatabase systems
People typically contrast SN with systems that keep a large amount of centrally-stored state information, whether in a database, an application server, or any other similar single point of contention.
Shared nothing architecture, where each processing unit has its own main memory and other storage.

Shard (database architecture)

shardingshardedshard
Google calls this sharding.
This is also why sharding is related to a shared nothing architecture—once sharded, each shard can live in a totally separate logical schema instance / physical database server / data center / continent.

Michael Stonebraker

Stonebraker, MichaelH-StoreMike Stonebraker
While SN is best known in the context of web development, the concept predates the web: Michael Stonebraker at the University of California, Berkeley used the term in a 1986 database paper.
In the C-Store project, started in 2005, Stonebraker, along with colleagues from Brandeis, Brown, MIT, and University of Massachusetts Boston, developed a parallel, shared-nothing column-oriented DBMS for data warehousing.

Distributed computing

distributeddistributed systemsdistributed system
A shared-nothing architecture (SN) is a distributed-computing architecture in which each node is independent and self-sufficient, and there is no single point of contention across the system.
Shared nothing architecture

MySQL Cluster

ClusterNDB
MySQL Cluster
MySQL Cluster is a technology providing shared-nothing clustering and auto-sharding for the MySQL database management system.

Oracle RAC

Oracle Real Application ClustersReal Application Clusters
Oracle RAC (Shared Everything)
Shared-nothing and shared-everything architectures each have advantages over the other.

Node (networking)

nodenodesnetwork node
A shared-nothing architecture (SN) is a distributed-computing architecture in which each node is independent and self-sufficient, and there is no single point of contention across the system.

Reliability engineering

reliabilityreliability theoryreliable
A shared-nothing architecture (SN) is a distributed-computing architecture in which each node is independent and self-sufficient, and there is no single point of contention across the system.

Application server

web application serverserversoftware platform
People typically contrast SN with systems that keep a large amount of centrally-stored state information, whether in a database, an application server, or any other similar single point of contention.

Single point of failure

single points of failurecentral point of failurecauses the entire circuit to "open" or stop operating
The advantages of SN architecture versus a central entity that controls the network (a controller-based architecture) include eliminating any single point of failure, allowing self-healing capabilities and providing an advantage with offering non-disruptive upgrade.

Self-management (computer science)

self-managementself-managingself-managing computer systems
The advantages of SN architecture versus a central entity that controls the network (a controller-based architecture) include eliminating any single point of failure, allowing self-healing capabilities and providing an advantage with offering non-disruptive upgrade.

World Wide Web

Webthe webweb-based
While SN is best known in the context of web development, the concept predates the web: Michael Stonebraker at the University of California, Berkeley used the term in a 1986 database paper.

University of California, Berkeley

BerkeleyUC BerkeleyUniversity of California
While SN is best known in the context of web development, the concept predates the web: Michael Stonebraker at the University of California, Berkeley used the term in a 1986 database paper.

Teradata

Teradata version 14Teradata AsterTeradata Corporation
Teradata, which delivered its first system in 1983, was probably one of those commercial implementations.

NonStop SQL

HP NonStop SQLTandem NonStop
Tandem Computers officially released NonStop SQL, a shared nothing database, in 1984.

Web development

developmentweb programmingwebsite development
Shared-nothing is popular for web development because of its scalability.

Scalability

scalablescalescale-out
Shared-nothing is popular for web development because of its scalability.

Google

Google Inc.Google, Inc.Googling
As Google has demonstrated, a pure SN system can scale simply by adding nodes in the form of inexpensive computers, since there is no single bottleneck to slow the system down.

Web application

web-basedweb applicationsweb app
There is some doubt about whether a web application with many independent web nodes but a single, shared database (clustered or otherwise) should be counted as SN. One of the approaches to achieve SN architecture for stateful applications (which typically maintain state in a centralized database) is the use of a data grid, also known as distributed caching.

Computer cluster

clusterclusteringclusters
There is some doubt about whether a web application with many independent web nodes but a single, shared database (clustered or otherwise) should be counted as SN. One of the approaches to achieve SN architecture for stateful applications (which typically maintain state in a centralized database) is the use of a data grid, also known as distributed caching.

State (computer science)

statestatefulstates
People typically contrast SN with systems that keep a large amount of centrally-stored state information, whether in a database, an application server, or any other similar single point of contention. There is some doubt about whether a web application with many independent web nodes but a single, shared database (clustered or otherwise) should be counted as SN. One of the approaches to achieve SN architecture for stateful applications (which typically maintain state in a centralized database) is the use of a data grid, also known as distributed caching.

Centralized database

centralized data managementcentralized database system
There is some doubt about whether a web application with many independent web nodes but a single, shared database (clustered or otherwise) should be counted as SN. One of the approaches to achieve SN architecture for stateful applications (which typically maintain state in a centralized database) is the use of a data grid, also known as distributed caching.

Data grid

There is some doubt about whether a web application with many independent web nodes but a single, shared database (clustered or otherwise) should be counted as SN. One of the approaches to achieve SN architecture for stateful applications (which typically maintain state in a centralized database) is the use of a data grid, also known as distributed caching.