liveBook · Manning

Denormalization

As explained in Building Web APIs with ASP.NET Core

Denormalization is the deliberate combination or duplication of related data to simplify retrieval or improve access performance.

Denormalization embeds related child data in a parent document instead of relying mainly on references between separate entities. This can produce a simpler schema with fewer collections and flexible documents. section 4.1.1

Board-game data

A document-oriented design can keep mechanics and domains inside board-game documents. A relational design instead uses separate tables and junction tables for those many-to-many relationships. section 4.1.1

Figure 4.2 MyBGList database schema diagram for a document-oriented NoSQL database
04-02

Compare the document-oriented board-game schema with the relational alternative. section 4.1.1

How Building Web APIs with ASP.NET Core covers it

How deep it goes
Explains parent-child embedding and contrasts schema structures, without detailing implementation or retrieval behavior.
Examples
Uses board games, mechanics, and domains to contrast embedded documents with tables and junction tables.
How it connects
Connects denormalization to NoSQL, document databases, relational databases, and many-to-many relationships.

Also explained in

Compare how 6 books explain denormalization →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Building Web APIs with ASP.NET Core. The section links point to the parts of the book it draws on.