CRUD (Create, Read, Update, Delete)

CRUD is the four-verb grammar of software data: create a record, read it, update it, delete it. Nearly every business application — from a S$10 to-do app to a national registry — is CRUD at scale with rules attached. Understanding it demystifies most of what software actually does all day.

What It Is

CRUD names the four basic operations on persisted data: Create (insert a new record), Read (retrieve it), Update (modify it), Delete (remove it). The acronym frames most application development: an API or application layer exposing these operations over a database, wrapped in business rules (who may create what, which updates require approval, what deletion legally means), validation, and audit. Related vocabulary: REST APIs conventionally map to CRUD (POST/GET/PUT/DELETE), and the observation that 'most enterprise software is CRUD with workflow' is both a joke and substantially true.

Why It Matters to You

CRUD framing gives executives a useful lens on scope and risk. Feature conversations become tractable: for this new object, who can create, who reads, what may be updated after the fact, and what does delete actually do? That last one carries surprising weight in regulated contexts — deletion is rarely simple (retention obligations, soft deletes that flag rather than remove, the right-to-be-forgotten mechanics under data protection law), and systems where 'delete' is ambiguous are systems with compliance exposure. Approval workflows, similarly, are CRUD plus state: the update that requires sign-off first.

When You'll Meet It

In requirements discussions and product scoping. The four-verb test — what happens on create, read, update, delete? — applied to any new data object surfaces most of the governance questions early.