MVP Architecture

suggest change


MVP is an architectural pattern, a derivation of the Model–View–Controller. It’s represented by three distinct components: Model, View and the Presenter. It was engineered to facilitate automated unit testing and improve the separation of concerns in presentation logic.

In examples you’ll find a simple project built with MVP pattern in mind.


Component duties:

| Model | View | Presenter | | —— | —— | —— | | Communicates with DB layer | Renders data | Performs queries to the Model | | Raising appropriate events | Receives events | Formats data from Model | | | Very basic validation logic | Sends formatted data to the View | | | |Complex validation logic| |||

Differences between MVC and MVP:

Feedback about page:

Optional: your email if you want me to get back to you:

Table Of Contents