liveBook · Manning

NoSQL database

As explained in Think Like a CTO

A NoSQL database stores data without requiring the fixed tabular structure and schema constraints typical of relational databases.

A NoSQL database stores documents in collections without requiring every document to have the same structure. It stores the data present in each document rather than placeholders for data that is absent. section 8.5.1

This distinguishes it from a relational database, which organizes similarly structured data into linked tables. When assessing storage options, ask whether the data shares a consistent set of attributes or varies substantially from record to record. section 8.5.1

Documents in one collection

Two documents can differ radically while remaining in the same collection; neither needs empty placeholders for attributes found only in the other. section 8.5.1

How Think Like a CTO covers it

How deep it goes
Defines documents and collections and contrasts their structure with tables, without detailing database operations or implementation.
Examples
Illustrates a collection whose documents can differ radically and need no placeholders for missing data.
What it assumes
Defines relational tables, rows, and columns alongside NoSQL rather than assuming those terms are known.
What you can do after
Evaluate/understand whether varying document structures make NoSQL worth considering instead of relational tables.
How it connects
Connects NoSQL databases to relational databases, SQL tables, files, data lakes, and data warehouses as alternative storage forms.

Also explained in

Compare how 7 books explain NoSQL database →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.