Find a data correctness recipe

Preserve identity, precision, concurrency, validation, and audit history

Represent values correctly

Problem	Recipe
Keep public IDs unchanged	Use opaque identifiers
Preserve currency precision	Submit money safely
Preserve time meaning	Send dates with zones
Seed initial server values	Pass server data

Problem	Recipe
Detect a stale edit	Handle edit conflicts
Handle a unique constraint race	Return uniqueness errors
Make a write repeatable	Use idempotency
Report partial batch results	Apply bulk actions

Problem	Recipe
Keep useful cached records	Cache reference data
Keep state across an expired session	Handle session expiration
Record a sensitive change	Write an audit trail
Change a contract safely	Use a compatible rollout

Was this page helpful?

Sorry to hear that. Please tell us how we can improve.