New Cohort Starts:

Donate
← Back to the skill map
Data & Storage/Data & services

Data Modeling

5 micro-topics in Data & Storage, each with the evidence that proves you have it and the written reason behind every link. Before you start, it rests on 2 other domains. Downstream, it holds up 4 domains.

5 topics  ·  depth 1–4 of 16  ·  4 internal links  ·  3 in  ·  4 out

Before you start

Load-bearing links first. Each one says what in this domain rests on what outside it, and why.

SQL

2 links

load-bearing

Normalize a schema rests on Query rows with SELECT

You normalize toward the queries you can write.

supporting

Denormalize deliberately rests on Read a query plan

Denormalization is justified by a measured read path.

Version Control

1 link

supporting

Version schema changes with migrations rests on Stage and commit changes

Migrations are versioned artifacts, and versioning habits carry over.

What you will be able to do

In prerequisite order. Each idea names the artifact that closes it, the market demand that put it on the map, and what it stands on.

Depth 1  ·  conceptual  ·  unassisted  ·  M07 §7.2

Normalize a schema

Removes duplication and update anomalies

Evidence
Designs a schema and defends its keys
Market anchor
Data modeling
Rests on
load-bearing

Query rows with SELECT · SQL

You normalize toward the queries you can write.

Depth 2  ·  conceptual  ·  unassisted  ·  M07 §7.2

Choose primary and foreign keys

Enforces identity and referential integrity

Evidence
Picks a key that survives a real-world edge case
Market anchor
Data modeling
Rests on
load-bearing

Normalize a schema

Normalization is defined by keys.

Depth 2  ·  conceptual  ·  guided  ·  M07 §7.2

Denormalize deliberately

Trades duplication for read speed knowingly

Evidence
Justifies a denormalization with a measured read path
Market anchor
Data engineering
Rests on
load-bearing

Normalize a schema

You cannot denormalize deliberately without the normal form.

supporting

Read a query plan · SQL

Denormalization is justified by a measured read path.

Depth 3  ·  representational  ·  unassisted  ·  M07 §7.2

Model one-to-many and many-to-many

Expresses cardinality in tables

Evidence
Implements a join table with correct constraints
Market anchor
Data modeling
Rests on
load-bearing

Choose primary and foreign keys

Cardinality is expressed with keys.

Depth 4  ·  procedural  ·  scaffolded  ·  M07 §7.2

Version schema changes with migrations

Applies and reverses schema changes in order

Evidence
Ships a migration that runs forward and back
Market anchor
Databases · DevOps
Rests on
load-bearing

Model one-to-many and many-to-many

Migrations change a schema you designed.

supporting

Stage and commit changes · Version Control

Migrations are versioned artifacts, and versioning habits carry over.

What rests on this domain

Everything downstream that names an idea here as a prerequisite, grouped by where it lives.

Data Ingestion

1 link

load-bearing

Build a repeatable ingestion pipeline rests on Choose primary and foreign keys

Idempotent loads require a key to upsert on.

Backend Testing

1 link

load-bearing

Test against a real database rests on Version schema changes with migrations

A test database is created and torn down by migrations.

Embeddings & Vectors

1 link

load-bearing

Store and query vectors in Postgres rests on Model one-to-many and many-to-many

Vectors live in a schema alongside their metadata.

API Contracts

1 link

supporting

Design an API contract rests on Model one-to-many and many-to-many

Resource shapes usually mirror the data model.

Retool. Retrain. Relaunch.

375 ideas. 17 weeks. No tuition, ever.

Vets Who Code is a veteran-run 501(c)(3). The accelerator is free, remote, and we don’t take a share of your first paycheck.

Free · Remote · 17 weeks · EIN 86-2122804