Block 1 · Week 3 · Databases and domain modelling
Databases and domain modelling
Your app can think. Now teach it to remember.
The lesson in one line
You cannot store what you cannot describe. Before any tool, answer three questions about your user's world, and the tables fall out of the answers. It is the move an FDE makes inside every customer's business: describe their world precisely before building the system around it.
1
What are the things?Nouns the app must create, find, change and delete on their own. Each gets a table.2
What does each thing have?The facts you need to recreate one. Each is a column.3
How do they connect?One-to-one, one-to-many, many-to-many. A pointer on the many side.01
Your path through this lesson
- Feel the app forget, then see rows survive
- Build Aarav's model by hand, sections 1 to 5
- Pass the six Arena briefs
- Model your own app
- Finish the practice set before you start the next lesson
02
When you need it
Do this
The Modelling Lab
Read
Notes
Practice
Practice set
Stuck
Troubleshooting
Roadmap
Back to the roadmap
Refresher
The second interface: APIs · your API table
A table is useless until you know the shape of what goes in it.Next: these tables, typed into Supabase, and a row that survives a refresh.