Is it true that >80% of the backend's work is to "saw" CRUD-API?

Question

Backend

Observing myself and my colleagues, I noticed that each project follows the same scenario:

• created models;
  
• wrote tests for them;
  
• wrote CRUD controllers for each model (accept data; connect to the database via ORM; render json);
  
• wrote tests for them;
  
• moved on to a new project;
  

Of course, there are more interesting tasks like:
write a deferred tasks worker; write a data aggregation script; configure morphological or prefix search; optimize endpoint operation in order to reduce response time; optimize the work of any script; etc;
But their number is not large in each project.
Interested in the experience of colleagues. Is this true or is the world of backend development more diverse?

Answer 1

The draft part of the business logic relies on the interaction of models, which as a rule should have something like CRUD. Often there is a lot of code writing, especially in the presence of various verifications, so their writing is noticeable by the time spent, and the highlights are they are a little earlier (architecture) and a little later (interaction, behavior), but hardly noticeable precisely due to a well-prepared foundation in the form of tested " bricks."

Answer 2

No, it's not. CRUD is a very small layer of tasks. It so happened that the business logic in the vast majority of cases goes beyond crud, so there are more tasks

Answer 3

On a modern project where there is a React / Vue / Angular SPA application, yes, the backend is needed to drive JSON to / from the client
. much moved to the front