Please tell me whether it is possible to create for each controller a service that will croning the logic of the controller to which it belongs. And can such a service contain non-reusable methods (methods that will be used in only one controller). If the above is unacceptable, then how to build the "Architecture" correctly - for this problem. Google write "business logic in the series" - what is meant by this term.?

  • Can a couple of examples of what you have difficulties7 - Sergey Rogachev
  • "business logic in services" is exactly what you described. All logic should be in services. In controllers, only the variables needed to work with the view . Controllers should be as thin as possible, i.e. contain as little logic as possible. The fact that the services will not be reused methods - do not worry. - Stepan Kasyanenko

0