Databases Deep Dive

A connected route from foundations to production systems: 4 stages and about 72 hours, including practice and projects. Learn, practise, and prove each stage.

Set a target
Your progress0 of 14 topics
Current stageRelational access

Stage 1 of 4

Your paceNot set

Set a target on the planner

Take the placement check (10 min)

Draft. This path has not been reviewed by a second person yet. Topic order, estimates and tasks may change.

Arrows run from a prerequisite to what it unlocks. Select a topic to open it.
Filled: doneHeavy outline: in progressDashed: waiting on a prerequisiteDotted: skipped

The list view has the same topics and works with any screen reader.

  1. Stage 1: Relational access

    3 topics · 12 h · milestone: Build a small order model and demonstrate a join, a constraint failure and a transaction rollback0 / 3
    Stage project and rubric

    Build a small order model and demonstrate a join, a constraint failure and a transaction rollback.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • The schema has keys and constraints, and a test shows one constraint refusing bad data.
    • A join returns the expected rows, including a row kept by an outer join where a value is missing.
    • A transaction that fails part-way leaves no partial change, and you show the before and after.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  2. Stage 2: Measure before tuning

    4 topics · 22 h · milestone: Submit before/after plans for five slow queries and identify which observed plan property changed0 / 4
    Stage project and rubric

    Submit before/after plans for five slow queries and identify which observed plan property changed.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • Each of the five queries has a before and after plan with real timings, not estimates alone.
    • For each, you name the plan property that changed (scan type, join method, rows estimated against rows read).
    • You show one change that did not help, and why the plan says so.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  3. Stage 3: Concurrency in practice

    3 topics · 16 h · milestone: Walk through two recorded transaction schedules0 / 3
    Stage project and rubric

    Walk through two recorded transaction schedules. Predict the result before revealing each step.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • Your predictions are written down before each step is revealed, and you mark which were wrong and why.
    • You explain one lock wait and the order of statements that would have avoided it.
    • You size a connection pool from stated numbers and say what happens above that size.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  4. Stage 4: Expressing and scaling queries

    4 topics · 22 h · milestone: Design a reporting query and partition strategy0 / 4
    Stage project and rubric

    Design a reporting query and partition strategy. Verify the output against a baseline, then defend one distribution trade-off.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • The reporting query returns exactly the baseline's rows, shown by count and checksum.
    • The partition or shard key is justified by the access pattern, with the skew you expect.
    • The schema change rolls through two application versions without downtime, step by step.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

Source inventory and coverage

14 topics map to 40 unique activities. Shared resources count once. Every topic has a self-check; every stage has a project rubric.

Supplementary pages kept outside this path:

Pages under Library and Practice come from, or build on, Donne Martin's System Design Primer (CC BY 4.0).

Esc
↑ ↓ to move↵ to open