Choosing the right database

Stage 1 · Lesson 2 of 6

Access patterns: the questions your app asks

Start from the data, not the product

An is a question your app asks its data again and again: "get this user by email", "list the last 20 orders for this shop", "search products by name", "total sales per day this month". Write them down before you choose anything, with a rough idea of how often each one runs.

The list tells you a lot. Lookups by one key suit almost any database. Lists filtered and sorted several ways need good .

Questions that combine many kinds of record favour . Questions over millions of rows at once point to analytics tools. A database that answers your top five patterns easily is a good fit, whatever its marketing says.

Common trapdesigning tables from the screens you imagine and discovering the real questions only after launch.

A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock

Resources for this stage

Start with· follow one of these

Practise

  • Pick any dataset and practise describing its shape, size and the questions you would ask of it

Keep handy

  • The data types chapter shows how much one relational database can store, JSON included

  • The data modelling introduction shows the same questions from the document side

Also worth your time

Mark this stage as not done?