This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.a_glossary:n:nosql [2021/06/15 14:03] char |
dido:public:ra:xapend:xapend.a_glossary:n:nosql [2022/04/25 14:57] (current) nick |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== NoSQL ===== | ===== NoSQL ===== | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary| Return to Glossary ]] | + | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] |
| - | **NoSQL** refers to a [[dido:public:ra:xapend:xapend.a_glossary:d:datastore]] that provides a mechanism for storage and retrieval of data that is modeled in means other than the tabular relations used in relational databases. Such databases have existed since the late 1960s, but the name "NoSQL" was only coined in the early 21st century, triggered by the needs of Web 2.0 companies. | + | **NoSQL** (Not SQL or Not Only SQL) is a generic term used for databases that do not depend on a relational model. The data does not need to have a strict schema or the usual SQL table structure. Most commonly, the data is aggregated as key-value pairs, JSON documents, graphs, or wide-column tables. |
| - | Source: [[https://en.wikipedia.org/wiki/NoSQL ]] | + | By using NoSQL databases, you can store immense volumes of unstructured data as it comes in and structures it at a later point. As expected, this leads to much better throughput, and read/write speeds, and allows you to scale out servers horizontally. |
| + | |||
| + | Non-relational databases, when applied in the right use-case environment, bring significant benefits in terms of performance and flexibility. However, not applying a schema at the data entry point also means it is more difficult to query NoSQL databases, maintain data consistency, and establish relationships between data sets. | ||
| + | |||
| + | Source: [[https://phoenixnap.com/kb/what-is-nosql ]] | ||