How to structure an enterprise MVC app, and where does Business Logic go?
- by James
I am an MVC newbie. As far as I can tell:
Controller: deals with routing requests
View: deals with presentation of data
Model: looks a whole lot like a Data Access layer
Where does the Business Logic go?
Take a large enterprise application with:
Several different sources of data (WCF, WebServices and ADO) tied together in a data access layer (useing multiple different DTOs).
A lot business logic segmented over several dlls.
What is an appropriate way for an MVC web application to sit on top of this (in terms of code and project structure)?
The example I have seen where everything just goes in the Model folder don't seem like they are appropriate for very large applications.
Thanks for any advice!