ASP.Net MVC Architecture
In this section, you will get an overview of ASP.NET MVC architecture. The MVC architectural pattern has existed for a long time in software engineering. All most all the languages use MVC with slight variation, but conceptually it remains the same.
Let’s understand the MVC architecture in ASP.NET.
MVC stands for Model, View, and Controller. MVC separates the application into three components – Model, View, and Controller.
Model: Model represents the shape of the data and business logic. It maintains the data of the application. Model objects retrieve and store model state in a database.
Model is a data and business logic.
View: View is a user interface. View display data using the model to the user and also enables them to modify the data.
A view is a User Interface.
Controller: Controller handles the user request. Typically, a user interacts with View, which in-turn raises appropriate URL request, this request will be handled by a controller. The controller renders the appropriate view with the model data as a response.
A controller is a request handler.
The following figure illustrates the interaction between Model, View, and Controller.
Asp.NET MVC Architecture
The following figure illustrates the flow of the user’s request in ASP.NET MVC:-
Request/Response in MVC Architecture
As per the above figure, when the user enters a URL in the browser, it goes to the server and calls an appropriate controller. Then, the Controller uses the appropriate View and Model and creates the response and sends it back to the user. We will see the details of the interaction in the next few sections.
Visit MSDN to learn MVC in detail.
I hope you liked this article based on asp.net mvc architecture tutorial. I would like to have feedback from my blog readers. Your valuable feedback, question, or comments about this article are always welcome.