---
title: 'CRUD Operations are Everywhere: DB and REST API Examples'
source: 'https://youtube.com/watch?v=ByuhQncSuAQ'
video_id: 'ByuhQncSuAQ'
date: 2026-08-02
duration_sec: 270
---

# CRUD Operations are Everywhere: DB and REST API Examples

> Source: [CRUD Operations are Everywhere: DB and REST API Examples](https://youtube.com/watch?v=ByuhQncSuAQ)

## Summary

This video explains the CRUD model (Create, Read, Update, Delete) and how it applies to software applications, databases, and REST APIs. It provides examples from everyday apps and database systems like SQL and DynamoDB, and shows how CRUD maps to HTTP verbs in API design.

### Key Points

- **CRUD Definition** [00:01] — CRUD stands for Create, Read, Update, Delete, and it describes the four basic operations performed on records in a database. Most software applications are CRUD applications.
- **CRUD in Everyday Apps** [00:14] — Examples include social media (creating posts, reading, updating, deleting), document editors (create, update, delete), and shopping baskets (add, edit quantity, remove).
- **CRUD in Databases** [01:10] — In SQL, CRUD maps to INSERT (create), SELECT (read), UPDATE (update), and DELETE (delete). NoSQL databases like DynamoDB use put item, get item, update item, and delete item.
- **CRUD in REST APIs** [01:53] — REST APIs expose resources (e.g., users, products, orders) and use HTTP verbs: POST (create), GET (read), PUT (update), PATCH (partial update), and DELETE (delete).
- **Soft Deletes** [03:11] — In practice, delete endpoints often perform a soft delete—updating a flag (e.g., 'isDeleted') instead of actually removing the record—to maintain data integrity and compliance.
- **Building an Application** [03:39] — The typical approach is to identify the data to store, build an API with endpoints for each CRUD operation, then build a front end on top to let users interact with the data.

### Conclusion

CRUD is a fundamental mental model for software development, applicable across databases, APIs, and front-end applications. Understanding it helps in designing any application that stores and manipulates data.

## Transcript

So today we're going to talk about crud 90% of the software that we use every day are what we call crud applications most of the time we're using them in software can be broken down into these four operations once you have
be really helpful when you come around to actually designing your own software so crud stands for create read update delete and it corresponds to what we do to records in the database if you're using an application that allows you to
chances are you're using us a crud application it's actually very difficult using crud in some form if you take you can obviously read them you can update them if you're paying Elon for
when you say something stupid and you hope no one else is going to notice even you create documents you obviously update them and you can delete them even shopping basket is following the crud model as well so you can add items to it
you can edit the quantity of them you can remove them as well so now you know using it in programming so as I mentioned earlier it's related to creating records in a database so when you come about storing data anywhere in
be using the crud model to do that so if you store data in SQL for example the statement obviously the select statement is your read statement there's an update statement as well and there's a delete statement it isn't just relational
databases that is using the crud model you can also see it in key value storage and no SQL options if you take Dynamo DB for example you can see the crud operations in action with put item get item update item and delete item if
any data in your application then it's good to think in terms of the crud model application but it isn't just the database where crud can be seen it's can obviously it's great being able to create a database and have items in the
database but you need to be able to access them somehow and usually the most common way to do this in a web application is using an API so most of creating what we call rest apis when you hear people talking about rest you often
hear the term resources which is really just a fancy name for storing data when you build out a rest API you will build out a endpoint for each of the resources if you're building out a shopping website for example your resources are
likely to be your users your products the orders the shopping basket that sort model each of these resources is going to be represented by a table in your to want to create read update and delete each of the records in your tables to do
this we create an endpoint for each operation for every single resource that endpoints to be able to interact with our domain model in rest we use what we our domain model in rest we use what we call the HTTP verbs so we have post get
put we also have patch and delete so if you imagine you're creating a user's post endpoint whenever you want to create a user you're going to have a get details and in some cases you might have
multiple users especially if you've got some admin back end you're going to have a put endpoint to be able to update the details of that user and in some cases you may have a patch endpoint which allows you to update individual Fields
finally you're going to have a delete endpoint that allows you to delete of a funny one because if you're dealing with relational databases or you need to maintain some data Integrity for some compliance reasons we rarely actually
delete the user because if you delete user then you're going to have to delete all of the orders that they've done as well and it gets a bit of a mess so even though you might have a delete endpoint on your API in reality it's probably
just going to update the record in your database with it is deleted Flack all of front end of your application so that users can interact with your application build an application from scratch then work out what all of your different
information that you want to store and then build out an API build out all the endpoints so you can interact with all of that data and then you can build a front end on top of that that allows users to actually use your application
programming that you really need to grasp and get your head around CU it's used everywhere and once you have that mental model in your head you can use it to create any application that you want to if you're new to programming then
need to know you also need to know about data structures and algorithms in which case you need to watch this video next thank you for watching and I'll see you thank you for watching and I'll see you in the next video