Data

Database operating model

• Measure cost against workload and utilization.
• Separate hot and cold data paths where needed.
• Keep schema changes reviewable and reversible.

Architecture notes

A healthy data platform balances throughput, durability, and simplicity.

• Favor predictable patterns over niche optimizations.
• Log enough context for diagnosis.
• Keep retention and backup strategy explicit.

Example metrics

• p95 latency
• replication lag
• database spend by environment
• failed migration attempts