Polyglot persistence matches different data workloads to different storage technologies instead of searching for one perfect database. A streaming service might use SQL for billing, NoSQL for watch progress, and a vector database for recommendations. section 8.10 section 8.2.6
The choice follows the business constraint: billing needs accurate transactions, watch progress prioritizes write speed at scale, and recommendations need semantic similarity. Each choice accepts a tradeoff; for example, watch progress can tolerate a small amount of lost data. section 8.2.6
Table 8.3 The Clarity Engineer’s Database Decision Matrix
|
The Question
|
SQL (The Accountant)
|
NoSQL (The Collector)
|
Vector (The Brain)
|
|
Data Type?
|
Structured with strict
relationships.
|
Variable or unpredictable JSON
documents
|
High-dimensional mathematical
embeddings
|
|
Consistency?
|
Absolute (ACID guarantees).
|
Flexible (BASE / Eventual).
|
Probabilistic (Approximate
matches).
|
|
Scaling Priority?
|
Integrity and complex joins.
|
Raw write speed and horizontal
scale.
|
Semantic similarity and intent.
|
|
Search Logic?
|
Exact keyword matching.
|
Key-value or field-based
filtering.
|
Semantic "neighborhood"
distance.
|
|
Maintenance?
|
High (Often needs a DBA for
complex tuning).
|
Low to Medium (Managed PaaS
options).
|
Medium (Usually requires an AI
service for embeddings).
|
|
Operational Overhead & Skill Required?
|
Low to Medium: Tooling is well
understood, standard SQL skills, and predictable migrations.
|
Medium: Requires tracking
schema drift in code and managing distributed clusters.
|
High: Requires specialized
expertise in vector indexing algorithms, RAM management, and AI pipeline
sync.
|
|
Cost?
|
Predictable. You pay for the
server size (CPU/RAM).
|
Scalable. Usually
"pay-per-request" or storage volume.
|
Premium. High RAM usage + cost
of AI embedding API calls.
|
|
Tradeoff?
|
You trade speed for Bulletproof
Accuracy.
|
You trade strict structure for Unlimited
Growth.
|
You trade literal truth (and cash!) for Human Meaning.
|
Compare SQL, NoSQL, and vector databases by data type, consistency, scaling priority, search, and maintenance needs. section 8.2.6
Specialized stores bring an operational tax: teams must learn different query languages and failure modes, coordinate deployments and migrations, and manage separate costs, monitoring, and backups. Before adding another engine, weigh its functional or performance gain against that overhead; if the benefit is not clear, keep the workload in the primary database. section 8.2.7
