Request flow used for ASP.NET MVC framework

Request flow handles the request from the clients and passes it to the server. The Request flow is as follows:

• Request is being taken from User to controller.

• Controller processes the request from the user and creates a data Model of that particular request. 

• Data model that is being created is then passed to View that handles the frontend or the design. 

• View then transforms the Data Model by using its own functions in an appropriate output format.

• The output format that is being given by the View is then gets rendered to the Browser and the View will be seen by the user. 

Now the question is,  how does this architecture work?

• The workflow of MVC architecture is given below, and we can see the request response flow of a MVC web application.

 

The figure is very self-explanatory and shows the work flow of MVC architecture. The client, which is the browser, sends a request to server (internet information server) and the Server finds a Route specified by the browser in its URL and through Route. The request goes to a specific Controller and then the controller communicates with the Model to fetch/store any records . Views are populated with model properties, and controller gives a response to the IIS7 server, as a result server shows the required page in the browser.