What problem does normalization actually solve?
Update, insert and delete anomalies caused by storing the same fact in more than one place. If a customer's address lives in every order row, changing it means updating many rows, and missing one leaves the database contradicting itself. Normalization gives each fact one home.
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.