Choosing the right database

Stage 2 · Lesson 2 of 6

Why PostgreSQL is usually the right default

Relational databases: the sensible default

For a new app with users, records and relationships, is the safest first choice for most teams in 2026. It is , follows the SQL standard closely and is offered as a managed service by every major cloud and by platforms such as Supabase and Neon.

It also covers jobs that once needed a separate system. It stores and indexes JSON. It has built-in full-text search.

The pgvector adds vector similarity search, and the extension adds maps and locations. That means one database can carry a project a long way, with one backup, one set of credentials and one query language. Start here unless your gives a clear reason not to.

Common trapadding a second database before the first one has shown a real limit.

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

  • CoursePaid
    Grokking Relational Database Design and Modeling

    Design Gurus · Intermediate · $98 one-time

    Data modelling, ER diagrams, keys and normalisation for the relational default, with worked designs

  • GuideFree
    PostgreSQL Tutorial

    PostgreSQL Global Development Group · Beginner

    The short official tutorial: create a database, tables and your first queries in an evening

Practise

  • Run SQL on PostgreSQL, MySQL or SQLite in the browser and compare how each handles JSON

  • Free interactive lessons if your SQL needs warming up before the hands-on task

Keep handy

Also worth your time

Mark this stage as not done?