When should I denormalize on purpose?
When measured read performance demands it, such as precomputed totals or flattened reporting tables, and you accept the duty to keep copies in sync. Normalize first, denormalize deliberately, and document which table is the source of truth.
Answered in
Database Normal Forms, Worked Through One Ugly Table1NF to 4NF are easier to remember as the specific anomaly each one removes. One messy orders table, fixed step by step, shows what each form is for.
Read the full analysisOther questions this article answers
More system design & architecture questions
- How much spare capacity should a gateway keep?
- Why are bounded queues important for availability?
- Should a load balancer always move requests away from an unhealthy server?
- Can a circuit breaker prevent every cascading failure?
- Why does pagination improve API performance beyond just 'smaller responses'?
- Why is asynchronous logging faster than writing logs synchronously?
- When does caching actually help API performance, and when doesn't it?
- Why does payload compression trade CPU time for network time, and when is that worth it?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.