CRUD
CRUD is short for create, read, update, and delete. These are four common ways to work with saved data, but CRUD is not an API protocol.
Another example
An asset system lets an authorized editor create a record. Auditors read its locked history, and editors update details. Admins soft-delete it after checking dependencies. Restore is a named action of its own. Not every business action is forced into one CRUD word.
Main parts
- 01Create
- 02Read and update
- 03Delete and lifecycle policy
Use it when
Use CRUD to list basic data powers and the authorization, checks, audit, and life-cycle rules for each one.
Do not use it when
Do not turn approve, refund, merge, or publish into a vague update. Each action has important rules of its own.
Name used in code
persistence operations mapped deliberately—not mechanically—to domain and HTTP operations Before you ship
Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback.
Outcome: Design or review CRUD for this system while keeping data correct, secure, and easy to operate. User context: An asset system lets an authorized editor create a record. Auditors read its locked history, and editors update details. Admins soft-delete it after checking dependencies. Restore is a named action of its own. Not every business action is forced into one CRUD word. Technical concept or control: CRUD. Why it fits: Use CRUD to list basic data powers and the authorization, checks, audit, and life-cycle rules for each one. Do not use it when: Do not turn approve, refund, merge, or publish into a vague update. Each action has important rules of its own. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.
Check this request
Review the current use of CRUD. Definition: CRUD is short for create, read, update, and delete. These are four common ways to work with saved data, but CRUD is not an API protocol. Release checks: Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.