Database Design Guide

Design Philosophy

Data outlives code. Your schema decisions today will constrain your options for years.

Core Principles

1. Model the domain, not the UI - Schemas should reflect business reality
2. Normalize first, denormalize with purpose - Start correct, optimize later
3. Indexes are not magic - They trade write speed for read speed
4. Plan for change - Migrations are inevitable

Data Modeling Process

Step 1: Identify Entities