KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
How would one typically implement a service layer in an MVC architecture? Is it one object that serves all requests to underlying business objects? Or is more like an object that serves different service objects that in their turn interact with business objects? So: Controller -> Service -> getUserById(), or: Controller -> ServiceManager -> getUserService() -> getUserById() Also, if the latter is more appropriate, would you configure this ServiceManager object in a bootstrap? In other words, register the different services that you will be needing for your app to the service manager in a bootstrap? If none of the above is appropriate, what would help me get a better understanding of how a service layer should be implemented? Thank you in advance.
Tags (comma-separated)
Save Edits
Cancel