Model View Controller Pattern has three goals – Clean Code, Manageable Code and Scalable Code – by clearly separating three aspects of any medium to very high complex solution – Business Logic, Data Access and User Interface. Leveraging OOPs concepts, this pattern focuses on creating an iron wall between data and the user’s interaction with it.

MVC Pattern has three main components as the name suggests – the Model manages the data and business logic of the solution based on the requests from the Controller. The View reads and interprets the data from the Model and passes on the instructions to the Controller. The Controller, the brain of the pattern, gets the instructions from the View, accesses data from the Model and responds to the View accordingly.

In SAP, the MVC pattern is vastly used in SAP UI5 and Fiori Applications leveraging OData Services used to get the data from the backend system. However, even in the programming model, MVC is used conceptually, building on OOPs. This allows developers to reuse the solution more optimally and take advantage of the scalability MVC provides.

MVC Pattern provides advantages like cleaner, maintainable and scalable design, separation of design concerns, and less design dependency leading to independent programming and quicker development.

~S