What characterizes a "basic CRUD" project?

Asked

Viewed 11,728 times

5

Round and a half comes up a question talking about application "basic CRUD".

I understand that the application contains basically the so-called "sign up screens", from which manipulate tables in which apply to four operations: Create (insert), Read (query), Update (update) and Delete (delete).

But the definition may not be very clear to some. Particularly I never had to implement these screens fully (by luck or by chance), so I don’t have the systemic view of how they are implemented.

Is there anything beyond that that’s important to know?

Something else that is implicit in said expression?

terminology crud
  • 1

    For me it is something very informal, CRUD is CRUD. Maybe basic is something that really is just very simple data, with minimal validation, without having to juggle the screens, probably an input master-Detail don’t tell. but you’ll know.

  • Something that that compares to criminal records with subitens? Like, there are registers where you should register the central information (header?) and a list of daughter information. For example, a product contains lots that in turn have distinct lot validations and lot numbers

  • Related: https://softwareengineering.stackexchange.com/questions/379067/what-is-a-crud-system

  • It would be convenient a description of what you consider "basic CRUD".

  • @Brewertonsantos I described how I could in the question, I have no more details because I made a.

2 answers

4

As described in blog article Wordpress Uncomplicated:

CRUD is the acronym for the English language expression, Create (Creation), Read (Query), Update (Update) and Delete (Destruction). This acronym is commonly used to define the four operations basic used in Relational Database.

Therefore, the term CRUD refers more to the operations, and not to the system itself, however, according to Wikipedia:

CRUD are the four basic operations used in databases provided to system users. Other acronyms can be used to define the same operations: ABCD: Add, Browse, Change and Delete BREAD: Browse, Read, Edit, Add and Delete VADE: View, Add, Delete, Edit.

One can then make a distinction between the types of query present in the system, I think then that a Basic CRUD system would be one that performs only these four operations without the use of other resources of relational databases. It is worth reading also the following article from Code Academy about CRUD and REST services: What is CRUD?

  • The problem with this definition is that it focuses on the explicit (which has already been mentioned in the question) and not on the implicit (the registrations, validations, etc. that eventually need to be done). It takes the experience of someone with a CRUD application to quote that implicit part. Regarding the argument that CRUD refers more to the database, in this case the question can be rephrased to "How would a simple CRUD-based application work"?

  • I think then the answer would be that it consists of an application with the elements of crud (create, read, update and delete records) and its business rules and specific data elements.

2

There are some types of pages that enter the concept of CRUD.

Of course, there are the main pages that justify the name CRUD (Creactive Read Update Delete) represented in DAO and DTO (Dminutes Toccess Thebject and Dminutes Transfer Thebject, respectively), but CRUD alone represents the form representing (computationally) and manipulating data. Overall in the MVC architecture (MOdel-View-Control) CRUD represents the layer between Model and View, being manipulated by Control.

To make this possible we need the pages that interact with CRUD the way the system should react, and that depends on the system (after all there are n forms of development, and the one that has taken more strength lately is the SPA - Single Page Application thanks to tools like Reactjs or Vuejs), and in this case the intermediate pages take over.

For example, imagine the data flow on a screen that shows users of a system and you need to make an interaction between the results of the database Querys on that intermediate page (like some more complex calculation that should be done before arriving at the View). then the flow would be: System prompts -> intermediate page selects which CRUD pages will be used -> CRUD reads database data (n readings of n tables, grouped or not) -> Data reaches the intermediate page and is processed -> processed data goes to higher layer (either direct to View or control to be reinserted into the view)

Browser other questions tagged terminology crud

You are not signed in. Login or sign up in order to post.