I've been covering different aspects of NoSQL in my running series here, which is targeted at beginners who want an entry-level view into databases. Also known as "non-SQL" or "non-relational", this category of database allows for the storage and querying of "schema-free" data — ie. data that is designed through a means other than the tabular model of relational databases.
Indeed — NoSQLs came around in the early 1990s to support features that were inherently difficult or unavailable via SQL's model, such as horizontal scalability. This need became radically greater with the internet's maturation; when managing unstructured/semi-structured data at massive volumes was pivotal — although there is debate at deeper levels on whether SQL vs. NoSQL is a valid line of demarcation regarding DevOps generally.
The four most common NoSQL database systems are: 1) keyvalue 2) document 3) graph 4) column. (But there are many more subsets, with 7 well-known ones.) For more on my CACM 'NoSQL series', you can visit these links:
Document-oriented databases store data as JSON rather than using columns/rows. It is a native form of data storage, of sorts, due to how it is widely used by the popular NoSQL and SQL systems.
This NoSQL database type is considered one of the four essential ones — so, no surprise, document databases are used by most popular non-relationals such as MongoDB, Cosmos DB, DocumentDB, Elasticsearch, OrientDB, PostgreSQL (which is foremostly SQL), RavenDB and SimpleDB.
Documents in and of themselves are at the root of document-oriented databases. How a document is defined will vary depending on the specific data store implemented. Documents are, however, typically used for encapsulating data into a standard encoding format. Common formats are XML, YAML, JSON, and the binary form, BSON.
Documents are roughly synonymous with objects, in their function. Organizationally, there is no need for a set schema — for instance, the fields inside each document are optional. Each document store can also hold different types of documents, often allowing you to encode separate documents via separate systems. Here is an example of a document being encoded using JSON:
"Address": "9 King's Cross",
Let's imagine the same document, but encoded via XML:
<phone type="Cell">(321) 555-0111</phone>
<phone type="Work">(333) 555-0000</phone>
<street1>9 King's Cross</street1>
<postcode> NW1 9TY</postcode>
The information is the same, but fields can differ. When you add new information to documents, there is no need to update every document's record, or to make sure they share a similar structure. (One difference between SQL and NoSQL is that relationals allow you to have some entries with no data entered inside fields, whereas documents can contain no empty fields.)
The way in which each document is structurally composed is usually referred to as that document's content, which can be referenced during querying/editing. For scalability, you can restrict updates to new entries rather than for the whole database. When making an add, change, query, or delete of information, you will be using a unique ID. Although each document has a unique identifier, you can simply use a number series or the complete pathway to reference documents. During queries, each document itself is searched — data is directly extracted from documents, rather than columns inside your database.
1. Limits of consistency checking
Because documents are not forced to have relations with one another, and each can have varying fields, this reduces consistency checks. For instance, in creating a book database containing author collections (with each collection containing associated documents/books) — it would be possible to bring up entries not associated with any author. There could also be duplications of author information.
This isn't an immense drawback in consistency in most contexts wherein you would use a document database, but for the highest level of RDB consistency audits (such as for accounting), it's anathema.
2. Weaker atomicity
Document databases are able to achieve eventual consistency. In the relational model, data can be modified from one place, without needing to use JOINs. A single command (such as deleting or updating a row) is able to affect all new reading queries, which will inherit this change.
In comparison, to make changes to collections of documents will need you to run separate queries per collection — which is a violation of atomicity requirements.
3. Security weaknesses
Nearly half of industries today — including the public services, manufacturing, healthcare, education, retail and utilities sectors — are exposed throughout the year, due to at least one serious exploitable web app vulnerability (Source: SecMag).
Let's run over a few great document database use cases examples, to place document databases into a concrete context. Overall — the commonalities of use, from Coca-Cola to eBay, is in giving more flexibility and cost-effective, feature-rich capabilities to developers — thereby growing the availability/performance of apps:
Document databases are particularly useful in app development. With the Apple App Store and Google Play Store containing a combined total of 33.6 billion app downloads, in Q1 of 2020 (Source: techjury) — document stores are/will continue to be a critical use case need for the majority of large businesses in most, if not all, industries.
With this increased demand, there's been a spike in the popularity of document stores on the market. And, while the main weakness of document stores is a relative lack of strong relational networks, this becomes its strength when dealing with large data volumes flexibly.
Alex Williams is a full-stack developer with over 15 years of experience, and the owner of Hosting Data UK.
No entries found