Feature Scaling vs Database Normalization
People hear normalization and think of one idea, and there are two. In machine learning, it means scaling number columns to a similar range. In databases, it means splitting tables so each fact is stored once. One changes the numbers. The other changes the table layout.
Feature Scaling
Puts number columns on one range. Then big numbers do not drown out small ones.
Feature scaling puts number columns on a similar range before training. One column might be age, from 0 to 100. Another might be income, up to 200,000. Without scaling, the big numbers can drown out the small ones. Min-max scaling squeezes each column to 0 to 1. Standardization shifts it so the average is 0 and most values sit near it.
Database Normalization
Setting up a database so each fact is kept in one place.
Normalization means each fact is kept in just one place in a database. Instead of copying a customer's city into every order, you keep it in the customers table and link to it. That way, a change happens once and nothing gets out of step. The rules come in steps called normal forms, such as first, second and third. Most apps aim for third normal form.
In one line
- Feature Scaling
- Puts number columns on one range. Then big numbers do not drown out small ones.
- Database Normalization
- Setting up a database so each fact is kept in one place.
These live in different corners of the glossary (AI and Development), which is exactly why they get confused.