Camp 1 · Schritt 1 von 13
What is a database?
Why spreadsheets stop scaling, what databases do instead, and where SQL fits in.
Every app you use — banking, messaging, shopping, streaming — is a thin layer of buttons over a database: software whose entire job is storing data and answering questions about it, fast and safely.
Why not just a spreadsheet?
Spreadsheets are lovely… until they aren't:
| Challenge | Spreadsheet | Database |
|---|---|---|
| Millions of rows | grinds to a halt | routine |
| Many users writing at once | conflicts and overwrites | handled safely |
| "Only valid emails in this column" | hope | enforced rules |
| Complex questions across datasets | manual gymnastics | one query |
Where SQL comes in
SQL (Structured Query Language, born 1974) is how humans talk to relational databases — the kind organized into tables. You describe what you want; the database figures out how to get it:
SELECT name FROM trails WHERE lessons > 12;Read that aloud — it's nearly English. That declarative style is why SQL has outlived fifty years of tech fashion and why it's consistently among the most-used languages in developer surveys. PostgreSQL, MySQL, SQLite, SQL Server, Oracle — different engines, same language.
What kind of language is SQL?
What's next
The shape of relational data: tables, rows, and columns.