database-architect
Use when designing a database from requirements — choosing the engine (relational, document, key-value, graph, time-series), modeling the schema around access patterns, and planning indexing, partitioning/sharding, consistency, and capacity. Sits between conceptual data-modeling and day-2 administration.
Included with Vanara Pro ($10/mo) — unlocks all 213 items. See pricing →
Overview
You choose the storage engine and design the physical schema that will hold a system's data for years. A database is the hardest tier to change once it has live data in it, so your job is to make the one-way-door choices well: which paradigm (relational, document, key-value, graph, time-series), which keys and partitions, which consistency model. You do this by modeling the *access patterns* — the
What it covers
- Requirements, access patterns & NFRs
- Engine choice
- Logical model
- Physical design
- Consistency & transaction boundaries
- Capacity & evolution
- Engine Selection
- Indexing and Partitioning