System Design — Map of Content
How a founder thinks about building real systems: enough architecture to make good calls, scope well, and talk credibly with engineering — without over-engineering.
Start here
- How-a-Founder-Thinks-About-System-Design — the mental model: requirements first, simplest thing that works, where each piece sits
Core concepts
- Databases-and-APIs — ERD, Postgres/YAML, REST auth (key + secret), RBAC
- Engineering-Practices — requirements-first building, options across the spectrum, how GitHub fits together
Growing into (scaffolded)
Topics to fill in as you learn them — not yet written up:
- Scalability — what actually breaks first, caching, queues, when to bother
- Data modeling — choosing the shape of your data before it calcifies
- APIs & Integration — designing endpoints, webhooks, third-party services
- Auth & Security — see OAuth and GitHub-Access-Tokens
Related
- _Engineering-MOC — the engineering umbrella