liveBook · Manning

Denormalization

Also called denormalized, denormalize

Denormalization is the deliberate combination or duplication of related data in a data model, often to simplify access or improve retrieval performance.

How 8 Manning books explain it

ScyllaDB in Action

Denormalization is a data-modeling technique that stores related data together, often duplicating information to support access patterns without additional lookups.

How it is used
Supports query-first ScyllaDB schemas by storing copies for each required way to read data.
How deep it goes
Explains partition-key-driven copies, write synchronization, primary-key differences, and partition-size trade-offs; defers automation details.
Examples
Uses article summaries copied into author, date, and score tables, plus author-name duplication to avoid N+1 lookups.
What you can do after
Build it from scratch by deriving access-specific tables and partition keys from application query requirements.

Read how ScyllaDB in Action explains denormalization →

Microservices Patterns, Second Edition

Denormalized data is data stored with deliberate redundancy to make retrieval more efficient.

How it is used
Uses denormalization to make high-volume queries efficient when joins or separate lookups are costly.
How deep it goes
Explains grouping and duplication in query views, including database constraints and the competing demands of queries and updates.
Examples
Illustrates an order grouped with its ticket and delivery, and a courier location copied into current deliveries.
What you can do after
Evaluate denormalization against normalized joins and choose a view grouping that balances query and update efficiency.

Read how Microservices Patterns, Second Edition explains denormalization →

Crack Any Codebase with AI

Denormalization is the deliberate duplication or flattening of data to reduce query work and improve read performance.

How it is used
Speeds high-volume analytics and filtering by serving joined data from one queryable table.
How deep it goes
Explains the read benefit, synchronization mechanism, and drift risk, but stops short of trigger implementation details.
Examples
Uses Cal.com's RoutingFormResponseDenormalized table and its trigger-maintained copy of joined routing-form data.
What you can do after
Evaluate read-performance designs by weighing skipped joins against synchronization failures and stale duplicated data.

Read how Crack Any Codebase with AI explains denormalization →

Microsoft Azure in Action

Denormalization is the intentional introduction of redundant or combined data into a relational schema to improve read performance or simplify access.

How it is used
Uses deliberate redundancy to simplify access and improve reads in relational schemas and Cosmos DB documents.
How deep it goes
Defines the technique and works through examples and trade-offs, without providing an implementation procedure.
Examples
Illustrates a post’s stored comment count and supplier details embedded in a product document.
What you can do after
Evaluate/understand when fewer joins or queries justify redundant data and its storage and consistency costs.

Read how Microsoft Azure in Action explains denormalization →

Grokking Relational Database Design

Denormalization is the deliberate introduction of controlled redundancy or less-normalized database structures to improve performance or meet operational needs.

How it is used
Improves query performance after normalization when frequent multi-table joins make application screens slow or expensive.
How deep it goes
Explains definition, decision steps, schema changes, query effects, and data-anomaly trade-offs, but stops short of implementation synchronization details.
Examples
Uses artist–album–song queries and user–payment_method–purchase receipt queries to demonstrate reduced joins and redundancy.
What you can do after
Evaluate and apply denormalization by identifying costly joins, adding selective redundancy, and checking data-change anomalies.

Read how Grokking Relational Database Design explains denormalization →

MongoDB 8.0 in Action, Third Edition

A denormalized data model stores related data together or redundantly to reduce the need for joins, separate queries, or cross-record operations.

How it is used
Reduces routine queries and updates by storing related data together in MongoDB documents.
How deep it goes
Explains embedding and referencing choices, their performance trade-offs, and the BSON document-size limit.
Examples
Uses a contact document with embedded address and access details, and child records accessed in a parent’s context.
What you can do after
Evaluate whether to embed related data or reference separate documents based on access patterns, duplication, and relationship complexity.

Read how MongoDB 8.0 in Action, Third Edition explains denormalization →

Effective Data Analysis

Denormalization is the deliberate combination or duplication of related data to reduce separation between tables and simplify analytical access.

How it is used
Reshapes source data into cohesive analytics tables that reduce joins and calculations for recurring queries.
How deep it goes
Defines strategic denormalization and star-schema roles, without specifying implementation steps.
Examples
Uses sales transactions or page views as facts, with customer or user attributes as dimensions.
What you can do after
Build analytics tables by selecting sources around recurring queries and valuable information.

Read how Effective Data Analysis explains denormalization →

Building Web APIs with ASP.NET Core

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

How it is used
Compares document-oriented data modeling with relational modeling through a board-game database example.
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.

Read how Building Web APIs with ASP.NET Core explains denormalization →

Also covered in

What to know first

Related concepts

Questions about denormalization

What is denormalization?

Denormalization is the deliberate combination or duplication of related data in a data model, often to simplify access or improve retrieval performance.

Which Manning books explain denormalization?

ScyllaDB in Action, Microservices Patterns, Second Edition, Crack Any Codebase with AI, Microsoft Azure in Action, Grokking Relational Database Design, MongoDB 8.0 in Action, Third Edition, Effective Data Analysis and Building Web APIs with ASP.NET Core.

What should I know before learning denormalization?

Manning books that teach denormalization usually introduce SQL, join, database table and caching first.

What is the difference between denormalization and database normalization?

Denormalization is the deliberate combination or duplication of related data in a data model, often to simplify access or improve retrieval performance. Database normalization is a relational database design technique that structures data to reduce redundancy and prevent dependency or update anomalies.

What is denormalization a kind of?

Denormalization is a kind of optimization. Optimization is the systematic selection or modification of values, configurations, or implementations to improve a defined objective, often subject to constraints.

What is denormalization also called?

Denormalization is also called denormalized or denormalize.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.