The MVC framework is named according to the MVC design pattern it follows. MVC stands for Model-View-Controller. An HTTP request is sent to a Controller, which is then mapped to a method inside the Controller class. Inside that method, the Controller decides what to do with the HTTP request. It then constructs a model that is agnostic to the Controller and request. The model brings all the logic together that contains the information the Controller needs. The view is then used to display the information contained inside the model to build an HTML page that gets sent back to the requesting client in the HTTP response. 

What the MVC framework allows us to do is separate the logic by letting each component of the framework focus on one specific thing:

• The Controller receives the HTTP request and builds a model
• The model contains the data we requested and sends it to the view
• The view then creates the HTML page from the data contained in the model