Normalized vs Denormalized Data
ref: https://medium.com/@katedoesdev/normalized-vs-denormalized-databases-210e1d67927d
in terms of a Relational Database
normalized database
- data starts from 1 table, and related data is put into different tables. "You get each piece of data through relationships to each table
- is slower than a denormalized table
- ideally all data is unique, you get what you want by jumping through relationships and links until you find it
denormalized database
- everything is in one table
- fast to retrieve
- you get stuff you don't need (redundant data)
- you also get stuff you might have duplicates of in other places
- joins will now need to be done in your application code