In computer programming, create, read, update, and delete (CRUD) are the four basic operations of persistent storage. CRUD is also sometimes used to describe user interface conventions that facilitate viewing, searching, and changing information using computer-based forms and reports. The term was likely first popularized by James Martin in his 1983 book Managing the Data-base environment.
Data can be put in a location/area of a storage mechanism.
- The fundamental feature of a storage location is that its content is both readable and updatable.
- Before a storage location can be read or updated it needs to be created; that is allocated and initialized with content.
- At some later point, the storage location may need to be destructed; that is finalized and deallocated.
Together these four operations make up the basic operations of storage management known as CRUD: Create, Read, Update and Delete.
Although relational databases are a common persistence layer in software applications, numerous other persistence layers exist. CRUD functionality can for example be implemented with document databases, object databases, XML databases, text files, or binary files.
Note: Some big data systems do not implement UPDATE, but have only a timestamped INSERT (journaling), storing a completely new version of the object each time.
|Create||POST, PUT if we have `id` or `uuid`|
In HTTP, the GET (read), PUT (create and update), POST (create - if we don't have `id` or `uuid`), and DELETE (delete) methods are CRUD operations as they have storage management semantics, meaning that they let user agents directly manipulate the states of target resources. The POST method, on the other hand, is a process operation that has target-resource-specific semantics which typically exceed the scope of CRUD operations.
This article possibly contains original research. (November 2018)
CRUD is also relevant at the user interface level of most applications. For example, in address book software, the basic storage unit is an individual contact entry. As a bare minimum, the software must allow the user to: 
- Create, or add new entries
- Read, retrieve, search, or view existing entries
- Update, or edit existing entries
- Delete, deactivate, or remove existing entries
Other variations of CRUD include:
- Martin, James (1983). Managing the Data-base Environment. Englewood Cliffs, New Jersey: Prentice-Hall. p. 381. ISBN 0-135-50582-8.
- Maryam Sulemani (7 April 2021). "CRUD operations explained: Create, read, update, delete". Retrieved 14 December 2021.
- Fielding, Roy (June 2014). "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, Section 4". IETF. Internet Engineering Task Force (IETF). RFC 7231. Retrieved 2018-02-14.
- Roy T. Fielding (2009-03-20). "It is okay to use POST". roy.gbiv.com. Retrieved 2020-04-14.
POST only becomes an issue when it is used in a situation for which some other method is ideally suited: e.g., retrieval of information that should be a representation of some resource (GET), complete replacement of a representation (PUT), or any of the other standardized methods that tell intermediaries something more valuable than “this may change something.” The other methods are more valuable to intermediaries because they say something about how failures can be automatically handled and how intermediate caches can optimize their behavior. POST does not have those characteristics, but that doesn’t mean we can live without it. POST serves many useful purposes in HTTP, including the general purpose of “this action isn’t worth standardizing.”
- Kann, Charles. Programming for the Web - From Soup to Nuts - Implementing a Complete GIS Web Page. Gettysburg College. pp. 6.1 CRUD Interface.
- Paul M. Jones (2008). "BREAD, not CRUD".
- McGaw, James (21 June 2010). Beginning Django E-Commerce. p. 41. ISBN 9781430225362.
- "CRAP and CRUD: From Database to Datacloud - Direct2DellEMC". Direct2DellEMC. 2012-11-13. Retrieved 2018-01-30.