Lopsis

Lesson 2.1

Normalisation and when to break it

Normalising removes duplicated truth. Denormalising trades that safety for read speed, and should be a decision rather than an accident.

Taught byDaniel OkaforTypeScript · PostgreSQL · API design · Data modelling
4m Intermediate 10,047 students

Overview

Normalising removes duplicated truth. Denormalising trades that safety for read speed, and should be a decision rather than an accident.

What this lesson covers

  • Remove duplicated data and update anomalies
  • Recognise when denormalisation is justified
  • Model many-to-many relationships properly

This lesson sits in Schema Design, part of PostgreSQL for Developers. It assumes what came before it and leads directly into the next lesson in the module.

In this lesson you will:

  • Remove duplicated data and update anomalies
  • Recognise when denormalisation is justified
  • Model many-to-many relationships properly

Resources