Orientation
The Capstone: Knowing vs Doing
You now know normalization, keys, grain, dimensional modeling, SCDs, warehouse architectures, NoSQL, graphs, MDM, mesh, features, and contracts. This final chapter answers the question all of that was for: faced with a real, vague modeling request, how do you actually produce a correct model, and explain it?
The gap between knowing concepts and applying them is where most people stall. Given "model our sales data," a beginner opens an editor and starts typing CREATE TABLE; a strong modeler runs a repeatable method, clarify, declare grain, choose a shape, handle history, and narrates the reasoning. This chapter is that method.
We pull every prior chapter into one workflow, show how to decide OLTP vs OLAP structure and why, walk a full worked example end to end, and teach how to narrate a modeling answer in an interview. By the end you should be able to take any prompt and drive it to a defensible model out loud.
Why it matters
This is the chapter that converts a library of techniques into a usable skill. The method here is what you actually run on the job and in interviews; the rest of the course is the depth behind each step.
Core mental model
Do not start at tables. Start at "what must this answer?", declare the grain, choose the shape for the workload, handle history, and narrate the tradeoffs.
- modeling method
- A repeatable sequence: clarify → grain → entities/keys → shape → history → evolve.
- requirements-first
- Deciding what questions the data must answer before designing any table.
- workload fit
- Choosing an OLTP or OLAP structure based on read/write patterns.
- narration
- Explaining the modeling reasoning out loud, the thing interviews actually grade.
Common mistake
Jumping straight to tables on any modeling prompt.
You bake in guesses about grain, history, and workload that are expensive to undo; method first.
Better habit
- Run the same method on every modeling question.
- Clarify and declare grain before designing anything.
- Narrate the reasoning and the tradeoffs, not just the schema.
Modeling skill is a repeatable process, not a memorized set of schemas. Master the process and you can model a domain you have never seen.
Treat the method as a checklist you run aloud. The worked example shows it applied; the interview section shows how to narrate it.
Practice prompts
- Recall the six method steps from memory.
- Explain why "method first" beats "tables first".
Remember this
Applied modeling is a repeatable method, clarify, grain, entities/keys, shape, history, evolve, narrated out loud; this chapter turns the whole course into that one usable workflow.