Design Patterns in Spring Boot projects

Question

In the last 12 months I have worked and studied to learn how to create REST Apis with Spring boot, before that I worked with php MVC programming to create web systems and now in this my "migration" for Java using Spring I’m having doubts/difficulty understanding if Spring uses some kind of Pattern design and what would be ?

I usually create classes that follow the following order: Restcontroller -> Service -> Repository and Domain and DTO classes for entities and entity conversion/formatting

This structure I’m using can be considered a design standard ? What would be ?

I think because I’m self-taught I still have this simple doubt about the most desirable people!

Answer 1

This structure I’m using can be considered a design standard ? What would be ?

Yes. This pattern you’re using is very close to what they call Transaction Script Pattern.

It’s a simple question, but the vast majority of professionals are not aware that this is an existing model and that it even has a name or often does not even know that there are other ways to organize the application.

I believe its popularity is due to the fact that it is simple to understand, apply and be a model that meets most applications well, such as explained by Fowler:

The glory of Transaction Script is its simplicity. Organizing Logic this way is natural for Applications with only a small amount of Logic, and it involves very little overhead either in performance or in understanding.