Choosing the right database

Stage 1 · Lesson 6 of 6

SQL versus NoSQL, without the myths

Start from the data, not the product

NoSQL is not one thing. It is a label for several families: document, key-value, wide-column and , each built for different jobs. Old arguments still circulate.

One is that NoSQL is always faster, but speed comes from matching the data model and indexes to the , not from the label. Another is that SQL cannot scale, yet run some of the busiest apps in the world. A third is that schemaless means no design, but a still needs a planned shape or the data becomes a mess.

Modern products also blur the lines: PostgreSQL stores and indexes JSON, and MongoDB supports multi-document . Compare specific databases for your specific access patterns.

Common trappicking a side in the debate instead of a tool for the job.

A question to check yourself, an AI practice session and 2 cheat sheet entries 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?