MVC and MVP both terms are correct but they have there own flavor. These are two different architectural pattern used in building a robust decoupled system in modern days. If you are building an application in a decoupled manner then definitely you will get following advantages --
1. It will decrease your maintenance cost.
2. Alteration and Modification will not hamper other modules thus making the developers life easy.
3. It will allow you to do parallel development and thus reducing the development time significantly.
and so on...
So basically MVC stands for Model View Controller and MVP stands for Model View Presenter.
The main difference between the two is how the manager (controller/presenter) sits in the overall architecture.
MVC pattern puts the controller as the main ‘guy’ in charge for running the show. All application request comes through straight to the controller, and it will decide what to do with the request. One of the old patter used to achieve separation of concerns.
MVP (Supervising Controller) on the other hand, doesn't mind for the View to take on a bigger role. View is the first object instantiated in the execution pipeline, which then responsible for passing any events that happens on itself to the Presenter. Advanced form of MVC.
View:
1. Renders data
2. Receives events
3. Have basic validations
4. Can interact with Model directly
Controller:
1. Helps view in complex design making tasks
2. Communicate with model
3. Performs complex validation tasks
Model:
1. Communicate with Database Layer and send appropriate data to the requester (View/Controller)
MVP :
View:
1. Renders data
2. Receives events
3. Have basic validations
Controller:
1. Helps view in complex design making tasks
2. Communicate with model
3. Performs complex validation tasks
Model:
1. Communicate with Database Layer and send appropriate data to the requester (Controller)
1. It will decrease your maintenance cost.
2. Alteration and Modification will not hamper other modules thus making the developers life easy.
3. It will allow you to do parallel development and thus reducing the development time significantly.
and so on...
So basically MVC stands for Model View Controller and MVP stands for Model View Presenter.
The main difference between the two is how the manager (controller/presenter) sits in the overall architecture.
MVC pattern puts the controller as the main ‘guy’ in charge for running the show. All application request comes through straight to the controller, and it will decide what to do with the request. One of the old patter used to achieve separation of concerns.
MVP (Supervising Controller) on the other hand, doesn't mind for the View to take on a bigger role. View is the first object instantiated in the execution pipeline, which then responsible for passing any events that happens on itself to the Presenter. Advanced form of MVC.
Individual responsibilities of each layers --
MVC :
1. Renders data
2. Receives events
3. Have basic validations
4. Can interact with Model directly
Controller:
1. Helps view in complex design making tasks
2. Communicate with model
3. Performs complex validation tasks
Model:
1. Communicate with Database Layer and send appropriate data to the requester (View/Controller)
MVP :
View:
1. Renders data
2. Receives events
3. Have basic validations
Controller:
1. Helps view in complex design making tasks
2. Communicate with model
3. Performs complex validation tasks
Model:
1. Communicate with Database Layer and send appropriate data to the requester (Controller)
No comments :
Post a Comment