Every account, order, message and post you've ever made in an app is stored somewhere. That somewhere is a database.
A great library doesn’t just pile books on the floor. It has a strict librarian. Every book gets a place, a card in the catalogue and a rule about where it goes. Ask for any book and it’s found in seconds.
A database is that library for an app. It’s an organised store of information that the app can search, add to and change very quickly. Your account, your orders and your messages all live in one.
What it does
- keeps information in a tidy, agreed shape
- finds exactly what's asked for, fast, even among millions of records
- stops two people changing the same thing at the same moment and making a mess
- keeps the information safe if the power goes off
Two common kinds
Some databases store things in tables, like very strict spreadsheets. Others store each item as a self-contained document. Both are just ways of keeping things findable.
What it isn’t
It isn’t a spreadsheet, even if it looks like one. A database is built for apps, many users at once and huge amounts of information.
Where the comparison breaks down
A librarian takes a minute to find a book. A database answers in a tiny fraction of a second, thousands of times a second.
How the words fit together
The backend keeps its information in a database. A schema is the database’s set of rules about what goes where. It all runs on a server.
Backups only count if you've tried restoring one. Many teams find out their backups were broken on the day they need them.

When you'll hear it
“It's stored in the database.” The information is saved in the app's organised store.
“Let me query the database.” Let me ask the store for some specific information.
“The database is slow.” Looking things up is taking too long, so the app feels sluggish.
“Where does our customer data actually live? When did we last check we could restore a backup?”

Try it yourselfReady to use it? The exact commands are on my other site, devcmds: Install SQLite ↗


