Denormalization
Denormalization is the deliberate combination or duplication of related data to simplify access, support particular access patterns, or improve performance.
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.
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
- Simplifies analytical access by combining related sources around cohesive topics and reducing joins and calculations.
- How deep it goes
- Defines denormalization and sketches star schemas, fact tables, and dimensions, but stops short of detailed implementation.
- Examples
- Uses sales transactions and page views as facts, with customer and user attributes as dimensions.
- What you can do after
- Apply it by selecting sources to combine according to recurring queries and valuable derived information.
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 →
Related concepts
- normalizationcontrasts with · Normalization is the process of transforming a value, representation, or data structure to satisfy a specified standard, scale, or structural constraint.
- database normalizationcontrasts with · Database normalization is a relational database design technique that organizes data into related tables to reduce redundancy and prevent update or dependency anomalies.
- joinaddresses · A join is an operation that combines records or rows from multiple data sources according to specified matching conditions or relationships.
- redundancyproduces · Redundancy is the presence of duplicate or overlapping information, components, or resources, whether intentional or unnecessary.
- optimizationkind of · Optimization is the systematic selection or adjustment of values, actions, or system designs to improve a specified objective, often subject to constraints.
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.