LESSON 2.1
Normalisation and when to break it
Learn key techniques and workflows in PostgreSQL for Developers.
3m
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.
In this lesson you will:
- Remove duplicated data and update anomalies
- Recognise when denormalisation is justified
- Model many-to-many relationships properly
Pro Tip
Use caching and revalidation wisely to ensure your app stays fast and data remains fresh without unnecessary requests.