Select optimal database architecture
databases-data-coreskillsetup L2★0
Sheshiyer/skill-clusters ↗What it does
Route database design decisions to correct store type
Best for
When designing schema or picking a store—stops you from solving the wrong problem with the wrong engine.
Inputs
- · workload pattern (transactional/analytical/cache)
- · access pattern (OLTP/OLAP)
Outputs
- · recommended store (PG/MySQL/Redis/ClickHouse)
- · index strategy
- · pool sizing rules
Preconditions
- · access pattern clearly identified
Failure modes
- · OLAP queries run on OLTP primary
- · Redis treated as system of record
- · unindexed foreign keys
Trust signals
- · expand-contract pattern for migrations
- · separate raw/derived/serving tables
- · batched idempotent writes