Maps 5–8
Map 5 — ACID / BASE / CAP
ACID → transaction promise
Atomicity | Consistency | Isolation | Durability
BASE → availability / softer consistency posture
Basically Available | Soft state | Eventual consistency
CAP → distributed partition trade-off
Consistency | Availability | Partition tolerance
Trap: CAP is not modeling cardinality and not a third transaction model parallel to ACID/BASE.
Source: pp. 176–180.
Map 6 — Environment Promotion Path
DEVELOPMENT → TEST / QA / UAT → PRODUCTION
first change formal proof live service / last stop
SANDBOX → isolated experiment / POC
may use protected/read-only data
NEVER writes back to Production
Interpretation: Build → Prove → Run; Sandbox explores beside the path.
Source: pp. 182–184.
Map 7 — Database Organization Spectrum + Workload Overlay
Hierarchical → rigid tree / parent-child
Relational → schema-on-write | usually row-oriented
Nonrelational→ schema-on-read possible | varied structures
ROW ORIENTED → OLTP-like: many columns, few rows per transaction
COLUMN ORIENTED → OLAP-like: few columns, many rows per scan
The categories can overlap; this is not one mutually exclusive taxonomy.
Source: pp. 180–186.
Map 8 — Lifecycle Disposition
RETENTION RULE: how long must data remain available?
↓
ACTIVE → ARCHIVE → PURGE
retrievable irreversible
Decision rule: if it still must be retrievable, do not purge it.
Source: pp. 186–188.