liveBook · Manning

Relational model

As explained in Grokking Software Architecture

A data model that represents information as relations, commonly implemented as tables linked through shared values.

Imagine finding Alice’s orders by following a maze of physical record paths. If the disk layout changes, the application can break. The relational model separates data from physical storage: it represents information in tables, or relations, linked by shared values. section 8.2.1

Figure 8.2 Showing how Primary Keys and Foreign Keys work together to link tables. The child table (Orders) uses the Customer_ID as a Foreign Key to point directly back to its parent record (Customers), establishing a clear one-to-many relationship.

An Orders table uses Customer_ID as a foreign key to link each order to a customer. One customer can have many orders. section 8.2.1

Normalization organizes data to reduce duplication and protect integrity. For example, keeping an address in one place helps avoid updating one copy while forgetting another. section 8.2.1

Relational queries are declarative: you specify what data you want, and the database engine decides how to retrieve it. SQL grew from the model’s mathematical foundations. section 8.2.1

How Grokking Software Architecture covers it

How deep it goes
Explains tables, keys, normalization, and declarative retrieval without formal set-theory derivations.
Examples
Illustrates customer orders linked by Customer_ID and an address-update anomaly.
What you can do after
Evaluate and understand how linked tables and normalization address data organization and update anomalies.
How it connects
Connects primary and foreign keys, normalization, data integrity, and declarative queries.

Also explained in

Compare how 3 books explain relational model →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.