---
id: "prereq-markdown-vs-sql"
type: "prereq"
source_timestamps: ["00:21:31", "00:23:45"]
tags: ["computer-science"]
related: ["concept-race-conditions-ai"]
reason: "Required to grasp why the Wiki approach fails in multi-agent scenarios due to race conditions."
sources: ["s11-wiki-vs-open-brain"]
sourceVaultSlug: "s11-wiki-vs-open-brain"
originDay: 11
---
# Markdown vs. SQL Databases

# Prerequisite: Markdown vs. SQL Databases

**Reason needed:** Required to grasp why the Wiki approach fails in multi-agent scenarios due to [[concept-race-conditions-ai]].

## What You Need to Know

The speaker contrasts folders of text files (Markdown) with structured databases (SQL).

### Markdown / Plain Text
- Unstructured.
- No native concurrency controls.
- Prone to overwrite errors when accessed simultaneously.
- Poor support for metadata-based queries (you can't easily say *show me all notes from Q1 about pricing*).

### SQL Databases
- Structured schemas with typed columns.
- ACID transactions.
- Row-level locking.
- Rich metadata querying.
- Native support for concurrent multi-agent access.

## Why This Matters in the Source

This distinction is the engineering foundation of:

- [[claim-wiki-breaks-at-scale]] — text files can't handle multi-agent concurrent writes or filter at high volume.
- [[claim-db-better-multi-agent]] — databases provide the concurrency controls multi-agent systems need.
- [[concept-openbrain-architecture]] — the database-first design.
- [[concept-hybrid-memory-architecture]] — uses SQL as truth, markdown as presentation.