Jump to content

NoSQL

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Sduplooy (talk | contribs) at 07:39, 20 September 2011 (→Document store: Added Raven DB to list.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
This article is about the class of database management systems. For the specific relational database management software, see NoSQL (RDBMS).
"Structured storage" redirects here and is not to be confused with COM Structured Storage.

In computing, NoSQL (sometimes expanded to "not only SQL") is a broad class of database management systems that differ from classic relational database management systems (RDBMSes) in some significant ways. These data stores may not require fixed table schemas, usually avoid join operations, and typically scale horizontally. Academia typically refers to these databases as structured storage,[1][2][3][4] a term that would include classic relational databases as a subset.

History

Carlo Strozzi used the term NoSQL in 1998 to name his lightweight, open-source relational database that did not expose an SQL interface.[5] (Strozzi suggests that, as the current NoSQL movement "departs from the relational model altogether; it should therefore have been called more appropriately 'NoREL', or something to that effect."[6])

Eric Evans, a Rackspace employee, reintroduced the term NoSQL in early 2009 when Johan Oskarsson of Last.fm wanted to organize an event to discuss open-source distributed databases.[7] The name attempted to label the emergence of a growing number of non-relational, distributed data stores that often did not attempt to provide ACID (atomicity, consistency, isolation, durability) guarantees, which are the key attributes of classic relational database systems such as IBM DB2, MySQL, Microsoft SQL Server, PostgreSQL, Oracle RDBMS, Informix, Oracle Rdb, etc.

In 2011, work began on UnQL (Unstructured Query Language), a specification for a query language for NoSQL databases.[8] It is built to query collections (versus tables) of documents (versus rows) with loosely defined fields (versus columns). So it is a superset of SQL where SQL is a very constrained type of UnQL where the queries will always return the same fields (same number, names and types). However, UnQL does not cover the DDL SQL statements like CREATE TABLE or CREATE INDEX[9].

Architecture

Typical modern relational databases have shown poor performance on certain data-intensive applications, including indexing a large number of documents, serving pages on high-traffic websites, and delivering streaming media.[10] Typical RDBMS implementations are tuned either for small but frequent read/write transactions or for large batch transactions with rare write accesses. NoSQL, on the other hand, can service heavy read/write workloads.[10] Real-world NoSQL deployments include Digg's 3 TB for green badges (markers that indicate stories upvoted by others in a social network)[11] and Facebook's 50 TB for inbox search.[12]

NoSQL architectures often provide weak consistency guarantees, such as eventual consistency, or transactions restricted to single data items. Some systems, however, provide full ACID guarantees in some instances by adding a supplementary middleware layer (e.g., AppScale and CloudTPS).[13][14] Two systems have been developed that provide snapshot isolation for column stores: Google's Percolator system based on BigTable,[15] and a transactional system for HBase developed at the University of Waterloo.[16] These systems, developed independently, use similar concepts to achieve multi-row distributed ACID transactions with snapshot isolation guarantee for the underlying column store, without the extra overhead of data management, middleware system deployment, or maintenance introduced by the middleware layer.

Several NoSQL systems employ a distributed architecture, with the data held in a redundant manner on several servers, often using a distributed hash table. In this way, the system can readily scale out by adding more servers, and failure of a server can be tolerated.[17]

Some NoSQL advocates[who?] promote very simple interfaces such as associative arrays or key-value pairs. Other systems, such as native XML databases, promote support of the XQuery standard.[citation needed] Newer systems such as CloudTPS also support join queries.[18]

Taxonomy

See also: Comparison of structured storage software

NoSQL implementations can be categorized by their manner of implementation:

Document store

Main articles: Document oriented database and XML database
Name Language Notes
BaseX Java, XQuery XML database
Apache CouchDB Erlang
eXist XQuery XML database
Jackrabbit Java
Lotus Notes LotusScript, Java, others MultiValue
MarkLogic Server XQuery XML database
MongoDB C++ BSON (Binary format JSON)
OrientDB Java
SimpleDB Erlang
Terrastore Java
Raven DB .Net

Graph

A separate article is available on Graph databases.

Name Language Notes
AllegroGraph SPARQL RDF GraphStore
DEX Java High-performance Graph Database
InfiniteGraph Java High-performance, scalable, distributed Graph Database
Neo4j Java
OrientDB Java
FlockDB Scala
Sones GraphDB C# Graph database with query language called GraphQL

Key-value store

Key-value stores allow the application to store its data in a schema-less way. The data could be stored in a datatype of a programming language or an object. Because of this, there is no need for a fixed data model.[19] The following types exist:

Eventually‐consistent key‐value store

Hierarchical key-value store

Hosted services

Key-value cache in RAM

Key-value stores on disk

Ordered key-value stores

Multivalue databases

Object database

Main article: Object database

Tabular

Tuple store

See also

References

  1. ^ Hamilton, James (3 November 2009). "Perspectives: One Size Does Not Fit All". Retrieved 13 November 2009.
  2. ^ Lakshman, Avinash; Malik, Prashant. "Cassandra — A Decentralized Structured Storage System" (PDF). Cornell University. Retrieved 13 November 2009. {{cite journal}}: Cite journal requires |journal= (help)
  3. ^ Chang, Fay. "Bigtable: A Distributed Storage System for Structured Data" (PDF). Google. Retrieved 13 November 2009. {{cite journal}}: Cite journal requires |journal= (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  4. ^ Kellerman, Jim. "HBase: structured storage of sparse data for Hadoop" (PDF). Retrieved 13 November 2009. [dead link]
  5. ^ Lith, Adam (2010). "Investigating storage solutions for large data: A comparison of well performing and scalable data storage solutions for real time extraction and batch insertion of data" (PDF). Göteborg: Department of Computer Science and Engineering, Chalmers University of Technology. p. 15. Retrieved 12 May 2011. Carlo Strozzi first used the term NoSQL in 1998 as a name for his open source relational database that did not offer a SQL interface[...] {{cite web}}: More than one of |pages= and |page= specified (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  6. ^ "NoSQL Relational Database Management System: Home Page". Strozzi.it. 2 October 2007. Retrieved 29 March 2010.
  7. ^ "NOSQL 2009". Blog.sym-link.com. 12 May 2009. Retrieved 29 March 2010.
  8. ^ http://unqlspec.org/display/UnQL/Home
  9. ^ Avram, Abel (04). "Interview: Richard Hipp on UnQL, a New Query Language for Document Databases". http://www.infoq.com. Retrieved 7 September 2011. {{cite web}}: Check date values in: |date= and |year= / |date= mismatch (help); External link in |publisher= (help); Unknown parameter |month= ignored (help)
  10. ^ a b Agrawal, Rakesh; et al. (2008). "The Claremont report on database research" (PDF). SIGMOD Record. 37 (3). ACM: 9–19. doi:http://doi.acm.org/10.1145/1462571.1462573. ISSN 0163-5808. {{cite journal}}: Check |doi= value (help); Explicit use of et al. in: |author= (help); External link in |doi= (help)
  11. ^ "Looking to the future with Cassandra | Digg About". About.digg.com. 9 September 2009. Retrieved 29 March 2010.
  12. ^ "Cassandra". facebook.com. 25 August 2008. Retrieved 19 August 2011.
  13. ^ "Datastore Agnostic Transaction Support for Cloud Infrastructures" (PDF). IEEE. 4 July 2011.
  14. ^ "CloudTPS: Scalable Transactions for Web Applications in the Cloud". Globule.org. Retrieved 29 March 2010.
  15. ^ "Large-scale Incremental Processing Using Distributed Transactions and Notifications". The 9th USENIX Symposium on Operating Systems Design and Implementation (OSDI 2010), Oct 4–6, 2010, Vancouver, BC, Canada. Retrieved 15 October 2010.
  16. ^ "Supporting Multi-row Distributed Transactions with Global Snapshot Isolation Using Bare-bones [[HBase]]" (PDF). The 11th ACM/IEEE International Conference on Grid Computing (Grid 2010), Oct 25-29, 2010, Brussels, Belgium. Retrieved 15 October 2010. {{cite web}}: URL–wikilink conflict (help)
  17. ^ "Cassandra: Structured Storage System over a P2P Network" (PDF). Retrieved 29 March 2010.
  18. ^ "Consistent Join Queries in Cloud Data Stores". Globule.org. Retrieved 31 January 2011.
  19. ^ Marc Seeger (21 September 2009). "Key-Value Stores: a practical overview". http://www.slideshare.net/marc.seeger/keyvalue-stores-a-practical-overview: slideshare. Retrieved 9 March 2010. Key value stores allow the application developer to store schema-less data. This data is usually consisting of a string that represents the key, and the actual data that is considered to be the value in the "key - value" relationship. The data itself is usually some kind of primitive of the programming language (a string, an integer, an array) or an object that is being marshalled by the programming languages bindings to the key value store. This replaces the need for fixed data model and makes the requirement for properly formatted. {{cite web}}: External link in |location= (help)
  20. ^ "Riak: An Open Source Scalable Data Store". 28 November 2010. Retrieved 28 November 2010.

Retrieved from "https://en.wikipedia.org/w/index.php?title=NoSQL&oldid=451463254"