Level 0 of 13 · about 2 weeks
How databases work
What a database management system actually is, the vocabulary of tables, rows and keys, where SQL fits, and the small bookstore database used as a running example for the rest of this roadmap.
Modules
Core: everyone needs it. Common: most jobs use it. Specialist: optional depth, safe to skip on a first read.
1
What a database is, and why not just files
what goes wrong when an application keeps its data in plain files, and what a database management system actually fixes
Core 6 parts · about 2 hours
2
The relational model in outline
tables, rows, columns, keys and schema diagrams, as a map of the vocabulary this subject keeps reusing
Core 5 parts · about 2 hours
3
Keys
super key, candidate key, primary key, foreign key and composite key, and why a table needs at least one
Core 5 parts · about 2 hours
4
The three-schema architecture
external, conceptual and internal levels, and the two kinds of data independence they make possible
Common 5 parts · about 2 hours
5
2-tier and 3-tier architecture
where the application layer sits, and how this is different from the three-schema data levels
Common 5 parts · about 2 hours
6
SQL in five minutes
SELECT, INSERT, UPDATE, DELETE, and the shape every query shares
Core 5 parts · about 2 hours
7
ACID, the one-paragraph version
atomicity, consistency, isolation and durability, as a preview of why transactions exist
Core 4 parts · about 2 hours
8
Relational versus NoSQL
document, key-value, graph and column stores at a glance, and when each one actually fits
Core 5 parts · about 2 hours
9
The running example for this roadmap
the full small bookstore database, assembled once, reused in worked examples through later levels
Core 5 parts · about 2 hours
10
DDL, DML, DCL, TCL
the standard classification of SQL commands, by what each one actually governs
Core 5 parts · about 2 hours