Strategic Denormalization

Concepts: dmDenormalization

When to Break the Rules Normalization optimizes for write safety. Denormalization optimizes for read performance. In data engineering, the majority of workloads are analytical (read-heavy), so strategic denormalization is not a shortcut. It is a deliberate architectural choice. The key word is 'strategic.' You must know what you are trading away. Every denormalized column is a consistency liability: if the source value changes, every copy must be updated. The question is whether the read performance gain justifies the update cost. The maintenance problem: every denormalized column needs a pipeline to keep it in sync. If the customer name changes in the source, your denormalized orders table still shows the old name until the next ETL run (or longer, if the pipeline breaks). You are trading