It is a software architecture used in app development. It is designed to manage the complexity of applications by separating the "layers" of code based on their function. The model layer implements domain-specific logic including business rules; the view implements any visual interactions (inputs and outputs); and the controller is the middle-ware that manages access to data (create, read, update, delete) and provides information to the input through the model.
to illustrate MVC
MVC: how user sees data
Model - represents the application data
View - represents the presentation on the UI layer
Controller - (the brains) business logic of the application
object relational mapping
Converts data between incompatible type systems to bridge the gap
EF - entity framework
EF is an object-relational mapper that enables developers to work with a database using .NET objects. It eliminates the need for access code that developers usually need to write.
MVC architecture was designed...
...to manage the complexity of applications by separating the "layers" of code based on their function (model, view, controller).
How does MVC work practically
User-generated events may cause a controller to change the model, or view, or
both. For example, suppose that the model stored the text that is being edited by the
end-user. When the user deletes or adds text, the controller captures the changes and
notiﬁes the model. The view, which observes the model, then refreshes its display,
with the result that the end-user sees the changes he/she made to the data. In this
case, user-input caused a change to both the model and the view.