Decisions · ten of them, one per page

Decisions

Ten decisions a database engineer has to make. Each page picks a side, names the price, and says what breaks when the choice is wrong. One decision is written so far. The rest are planned, in the order I intend to write them.

The list

All ten decisions

  1. Decision 1, Commit path and durability. Planned.
  2. Decision 2, Synchronous replication and failover. Ready. Read it. What a commit waits for before it returns, and what that choice costs when a server dies.
  3. Decision 3, Backup, PITR, and restore time. Planned.
  4. Decision 4, Online schema change. Planned.
  5. Decision 5, Capacity planning and growth curves. Planned.
  6. Decision 6, Multi-region and latency budgets. Planned.
  7. Decision 7, Multi-tenancy and the noisy neighbor. Planned.
  8. Decision 8, Connection management and pooling. Planned.
  9. Decision 9, Observability. Planned.
  10. Decision 10, Cost model. Planned.

Each decision page follows the same shape: what the choice is, why it matters, how each engine does it, when to use it, what breaks, the alternatives rejected, how to operate it, and the version notes. The numbers on a decision page are derived from stated assumptions until the Tested on box on that page says otherwise.