Head First Servlets and JSP, 2nd Edition

Model, View, Controller (MVC)

Use the MVC pattern to create a logical structure that separates the code into three basic types of components (Model, View, Controller) in your application. This increases the cohesiveness of each component and allows for greater reusability, especially with model components.

Model, View, Controller features

• Views can change independently from controllers and models.

• Model components hide internal details (data structures), from the view and controller components.

• If the model adheres to a strict contract (interface), then these components can be reused in other application areas such as GUIs or J2ME.

• Separation of model code from controller code allows for easier migration to using remote business components.

Model, View, Controller principles

• Model, View, Controller is based on:

  • separation of concerns

  • loose couplings

• Increases cohesion in individual components.

• Increases the overall complexity of the application. (This is true because even though individual components become more cohesive, MVC adds many new components to the application.)

• Minimizes the impact of changes in other tiers of the application.