Databases Basics
A database is where an app’s data lives so it survives between sessions — and can be searched. Close the app, reopen it tomorrow, and your tasks, notes and settings are still there.
Two Big Families
Most databases fall into one of two camps. Knowing which is which is half the battle.
Everything Is CRUD
Almost every app does just four things to its data. Learn these and you understand what a database is for.
- Create — add a new record
- Read — look one up or search for it
- Update — change an existing record
- Delete — remove it
When Each Fits
The shape of your data usually decides for you.
Start Simple
A builder’s instinct: begin with the simplest thing that works — even SQLite, a whole database in a single file — and only add complexity when you actually need it. Most first projects never outgrow it.
Sketch a Schema
How to implement: list the “things” your tool stores, and write one line of fields for each — e.g. Task: id, title, status, week. That’s your first schema.
- Weekly AI Tasks tracker — naturally relational: Main Tasks, daily entries, and notes that link to them. A small SQL database fits well.
- Personal brand site — usually needs no database at all; the content lives in files, which is simpler and cheaper.
What you learned
A database keeps data between sessions. There are two families — SQL/relational and NoSQL — every app does CRUD, and the builder’s move is to start simple and grow only when you must.