These days, all I hear is how MVC should contain additional layer called services, turning it into SMVC. But to me, it seems like too much of a decoupling and instead want to engineer my app something like this (example for changing user name)
- View sends new input to Controller
- Controller sends the request to Model with data it recieved to one central method of Model
- Model takes this data and internally processes it with its methods, and returns the data to controller
- Controller tells the View to update was completed and to update the View
- View updates itself with data given by Controller
I have been told that Model should not directly work on data either and instead should use Service layers to handle the bussiness logic, so the flow would change like this
- Controller sends the data to Model
- Model calls respective Service to process the data
- Model updates the data after Service processes them Rest is the same
For me, the first solution seems more elegant and the later seems like making a Model another Controller with data relying on Services, which is kind of weird logic and adds another layer of complexity to the whole app.
