Content deleted Content added
m Dating maintenance tags: {{Fact}} |
|||
(9 intermediate revisions by 9 users not shown) | |||
Line 1:
{{Short description|
{{Essay-like|date=May 2012}}
{{Memory types}}
Line 8:
|edition = Distributed Storage: Concepts, Algorithms, and Implementations
|ol = 25423189M
}}</ref> It is usually specifically used to refer to either a [[distributed database]] where users store information on a ''number of nodes'', or a [[computer network]] in which users store information on a ''number of peer network nodes''.
==Distributed databases==
Line 36:
In peer network data stores, the user can usually reciprocate and allow other users to use their computer as a storage node as well. Information may or may not be accessible to other users depending on the design of the network.
Most [[peer-to-peer]] networks do not have distributed data stores in that the user's data is only available when their node is on the network. However, this distinction is somewhat blurred in a system such as [[BitTorrent (protocol)|BitTorrent]], where it is possible for the originating node to go offline but the content to continue to be served. Still, this is only the case for individual files requested by the redistributors, as contrasted with networks such as [[
Distributed data stores typically use an [[error detection and correction]] technique.
Line 97:
|
| used by [[Amazon.com|Amazon]]
|-▼
| [[Container_Linux#ETCD|etcd]]
| {{free|[[Apache License 2.0|AL2]]}}
| {{yes}}
|
|-
| [[Hazelcast]]
Line 121 ⟶ 126:
| {{free|[[GPL 2]]}}
| {{yes}}
| SQL and NoSQL APIs
▲|
|-
| [[Riak]]
Line 134 ⟶ 139:
|
|-
| [[ScyllaDB]]
| {{free|[[GNU Affero General Public License|AGPL]]}}
|
Line 161 ⟶ 166:
* DeNet
* [[Storage@home]]
* [[Tahoe-LAFS]]
* [[Winny]]
Line 170 ⟶ 174:
* [[Cooperative storage cloud]]
* [[Data store]]
* [[Keyspace (distributed data store)|Keyspace]], the DDS [[Schema (database)|schema]]
* [[Distributed hash table]]
* [[Distributed cache]]
|