It depends on the type of application you are working with. If the application is a lightweight application and will not be supported for many years or does not need the flexibility of many changes to business requirements, you can almost put your logic anywhere!
Having said that there are very few such applications (if you intend to earn a living) that do not need flexibility. So, something that may seem naive at the moment, but otherwise it will turn out differently.
The approach to the name of the template Service is good, but I would suggest you read this article on Domain Driven Design , and this is related to fooobar.com/questions/751552 / .... Again, DDD may be redundant for a lightweight application, and the traditional controller, Service, DAO should be good enough.
Hope this helps.
source share