MVC patter is a design patter which helps us to structure our projects. It breaks down the projects to 3 parts Model, View and Control.

Model is responsible for : to all the data-related logic that the user works with.

View: The View component is used for all the UI logic of the application. For example, the Customer view will include all the UI components such as text boxes, dropdowns, etc. that the final user interacts with.

Controllers act as an interface between Model and View components to process all the business logic and incoming requests, manipulate data using the Model component and interact with the Views to render the final output.

I would try to explain this with an analogy:

It's like a restaurant.

• Controller : it's the waiter/waitress who takes your order (request)
• Model : it's the kitchen where the waiter sends your order to, they prepare the menu you ordered
• View : it's how presented is the food (plate, knife,fork) that you receive from the waiter/waitress for you to enjoy.

Here's my stab at it...

Model: Your data source or destination, be it a database, file, cache, etc, and the logic that directly interacts with the source/destination.

View: The consumer's interface with your application, where they see your output and put in their input.

Controller: The bridge between, that which determines what models are needed for which parts of the view.