A database is simply where your site remembers things: customers, orders, bookings, messages. The choice sounds technical, but for a first project it is mostly about how much you want to look after.
Here is a plain way to decide, plus what to ask for when you describe your site to Uttra.
If you are a beginner, start with SQLite: it is a single file, needs no server and is enough for a small shop, blog or booking site. Move to Postgres when many people write data at the same time or you outgrow one file.
SQLite: the simple default
SQLite stores everything in one file next to your project. There is no separate server to start, secure or pay for, which removes a whole group of things that can break.
It handles reading very well and is fine for thousands of visitors on a typical small site. Its limit is many simultaneous writes, such as a busy shop with orders arriving every second.
- Good for: portfolios, small stores, internal tools, booking pages, prototypes.
- Backup is copying one file, which is easy to automate.
Postgres: when you need more room
Postgres runs as its own server and is built for many users writing at once, larger data and more advanced queries. It is the usual step up when a project becomes a real business.
It adds moving parts: a server to keep running, a connection string to protect, and backups to plan. Do not start here only because it sounds more professional.
What about MySQL and the others?
MySQL is similar in spirit to Postgres and is common on traditional hosting. Document databases suit data that changes shape often. For a beginner these are rarely the first choice; pick them only if you already use a tool or host that requires one.
If you name a specific database when you describe your site, Uttra can build with that one. If you name none, a simple option is chosen for you.
Where the data lives matters too
Customer data is personal data. In the Gulf, laws such as Saudi Arabia's PDPL pay attention to where data is stored and who can access it. Know where your database physically sits and who has the keys.
This is general information, not legal advice. For sensitive data such as health or finance, speak to a professional before you collect it.
- Never keep the only copy of your data on a laptop.
- Keep passwords and connection strings as project secrets, never in code.
- Test a backup restore once, not just the backup.