Nick Rue · Full-stack freelancer
Case study · production code

Database design across Postgres, DuckDB and SQLite

Outcome: 27 numbered, repeatable migrations across two Postgres databases, and 5 databases restored clean in a backup drill.

How it works

  1. Model the data and its relationships.
  2. Write numbered migrations.
  3. Pick the right engine per job: Postgres, DuckDB or SQLite.
  4. Add full-text search and analytics queries.
  5. Back up and test the restore.

Open the live demo[Postgres, DuckDB, SQLite]

Screens

Database design across Postgres, DuckDB and SQLite screen
Database design across Postgres, DuckDB and SQLite screen
Database design across Postgres, DuckDB and SQLite screen

Want this for your business?

Tell me what you would change and I will scope it in a reply.

Start a project