Series

Data That Must Survive

Identifiers, clocks, migrations, constraints, and queries all have to respect one awkward fact: the data will probably outlive the code that wrote it.

  1. Let the Database Reject Impossible State
  2. A Transaction Defines What Must Succeed Together
  3. A Migration Is a Production Change
  4. Null Is a Domain Decision
  5. Money Is Not a Floating-Point Number
  6. Time Zones Are Part of the Data Model
  7. An Identifier Should Outlive Its Storage Engine
  8. Soft Deletes Preserve Ambiguity Too
  9. Pagination Needs a Stable Order
  10. An Index Must Serve a Real Query
  11. Audit History Is Different from Application Logging
  12. Data Outlives the Code That Created It