Contents
Which part of MVC software design is responsible for data?
view component
Data representation is done by the view component. It actually generates UI or user interface for the user. So at web applications when you think of the view component just think the Html/CSS part.
What are the main logics behind MVC architecture?
The Model-View-Controller (MVC) is an architectural pattern that separates an application into three main logical components: the model, the view, and the controller. Each of these components are built to handle specific development aspects of an application.
Where to put business logic in MVC approach?
The result, if you are following an MVC approach without also separating the application into tiers is that you end up with Models, Views, and Controllers that have bits of business rules and data access logic mixed in with the rest of the logic.
Is it possible to use MVC without data access logic?
It is entirely possible to design an application following an MVC approach without separating business logic and data access logic from the presentation layer and thus end up with a single tier design.
When to use MVC in view and controller?
So, to your view and controller, it should make no difference, if the data comes from a database or from a webservice or is even totally random, therefore you should do it in model. MVC is a presentation pattern, that only separates the different representation layers. It does not mean, that model has to be a uniform mess of spaghetti code.
Where to put business logic in C #?
Any validation needs to be handled by IValidatable on the Model. Any business logic needs to be routed to a separate layer. The general answer I have is that business logic normally fits into two categories: Object Oriented Business Logic: Gets modeled as objects (in the model), usually injected as repositories.