CRUD
Definition
CRUD stands for Create, Read, Update, Delete, representing the four essential operations for managing and manipulating data in databases effectively.
Use Cases
- GitHub: Managing issues and pull requests (create an issue/PR, view lists and details, edit titles/descriptions, close or delete where permitted). — GitHub exposes CRUD-style operations through its web UI and REST/GraphQL APIs backed by persistent data stores and authorization checks to control who can create, read, update, or delete resources. (Enables collaborative software development workflows at scale by making core objects (issues, PRs, comments) easy to manage programmatically and through the UI.)
- Shopify: Product catalog management for merchants (create products, read product listings, update prices/inventory, delete or archive products). — Shopify provides admin interfaces and APIs that support CRUD operations on commerce resources (products, variants, orders), with validation and role-based access to protect data integrity. (Lets merchants maintain accurate catalogs and inventory, improving storefront accuracy and operational efficiency.)
- Salesforce: Customer relationship management records (create leads/contacts, read account histories, update opportunities, delete or merge duplicates under governance). — Salesforce implements CRUD permissions at the platform level (object and record access) and exposes CRUD operations via UI and APIs, enforcing security and auditability. (Standardizes how customer data is managed across teams, improving data consistency and enabling automation and reporting.)
Frequently Asked Questions
- What's the difference between CRUD and REST?
- CRUD describes the four basic data operations: create, read, update, and delete. REST is an API design style that often maps HTTP methods to CRUD (POST=create, GET=read, PUT/PATCH=update, DELETE=delete). You can implement CRUD without REST (for example, via GraphQL or direct database access), and you can build REST APIs that do more than simple CRUD.
- When should I use CRUD?
- Use CRUD when your application needs straightforward management of stored data, such as user profiles, blog posts, inventory items, or support tickets. CRUD is a good fit when data can be modeled as records/documents and users need predictable actions (add, view, edit, remove). If your domain is heavy on complex workflows (approvals, state machines, event-driven processes), you may still use CRUD for storage but add workflow logic on top.
- How much does CRUD cost?
- CRUD itself is a concept and has no direct cost. Costs come from the services used to implement it: database/storage charges (capacity, reads/writes, backups), API/compute charges (serverless functions, containers, VMs), and networking (data transfer). Pricing depends on request volume, data size, read/write patterns, and whether you need high availability, replication, or caching.
Category: software
Difficulty: basic
Related Terms
See Also