mirror of
https://github.com/tiennm99/java-design-patterns.git
synced 2026-05-14 10:58:42 +00:00
docs: update mvc
This commit is contained in:
Ilkka Seppälä
@@ -3,22 +3,26 @@ title: Model-View-Controller
|
||||
category: Architectural
|
||||
language: en
|
||||
tag:
|
||||
- Decoupling
|
||||
- Architecture
|
||||
- Client-server
|
||||
- Decoupling
|
||||
- Layered architecture
|
||||
- Presentation
|
||||
---
|
||||
|
||||
## Also known as
|
||||
|
||||
* MVC
|
||||
|
||||
## Intent
|
||||
Separate the user interface into three interconnected components:
|
||||
the model, the view and the controller. Let the model manage the data, the view
|
||||
display the data and the controller mediate updating the data and redrawing the
|
||||
display.
|
||||
|
||||
To separate an application into three interconnected components (Model, View, Controller), enabling modular development of each part independently, which enhances maintainability and scalability.
|
||||
|
||||
## Explanation
|
||||
|
||||
Real-world example
|
||||
|
||||
> Consider ICU room in hospital which displays the patients health information on device displays which
|
||||
> are taking input from sensors connected to patient. Here, display's job is to display the data that
|
||||
> it receives from the controller which in turn gets update from sensor model.
|
||||
> Consider ICU room in hospital which displays the patients health information on device displays which are taking input from sensors connected to patient. Here, display's job is to display the data that it receives from the controller which in turn gets update from sensor model.
|
||||
|
||||
In plain words
|
||||
|
||||
@@ -26,53 +30,24 @@ In plain words
|
||||
|
||||
Wikipedia says
|
||||
|
||||
> Model–view–controller (MVC) is commonly used for developing user interfaces that divide the
|
||||
> related program logic into three interconnected elements. This is done to separate internal
|
||||
> representations of information from the ways information is presented to and accepted from the user.
|
||||
> Model–view–controller (MVC) is commonly used for developing user interfaces that divide the related program logic into three interconnected elements. This is done to separate internal representations of information from the ways information is presented to and accepted from the user.
|
||||
|
||||
**Programmatic Example**
|
||||
|
||||
Consider following `GiantModel` model class that provides the health, fatigue & nourishment information.
|
||||
|
||||
```java
|
||||
@Getter
|
||||
@Setter
|
||||
@Builder
|
||||
@AllArgsConstructor
|
||||
@NoArgsConstructor
|
||||
public class GiantModel {
|
||||
|
||||
private Health health;
|
||||
private Fatigue fatigue;
|
||||
private Nourishment nourishment;
|
||||
|
||||
/**
|
||||
* Instantiates a new GiantModel.
|
||||
*/
|
||||
public GiantModel(Health health, Fatigue fatigue, Nourishment nourishment) {
|
||||
this.health = health;
|
||||
this.fatigue = fatigue;
|
||||
this.nourishment = nourishment;
|
||||
}
|
||||
|
||||
public Health getHealth() {
|
||||
return health;
|
||||
}
|
||||
|
||||
public void setHealth(Health health) {
|
||||
this.health = health;
|
||||
}
|
||||
|
||||
public Fatigue getFatigue() {
|
||||
return fatigue;
|
||||
}
|
||||
|
||||
public void setFatigue(Fatigue fatigue) {
|
||||
this.fatigue = fatigue;
|
||||
}
|
||||
|
||||
public Nourishment getNourishment() {
|
||||
return nourishment;
|
||||
}
|
||||
|
||||
public void setNourishment(Nourishment nourishment) {
|
||||
this.nourishment = nourishment;
|
||||
}
|
||||
|
||||
@Override
|
||||
public String toString() {
|
||||
@@ -139,22 +114,50 @@ public class GiantController {
|
||||
```
|
||||
|
||||
## Class diagram
|
||||
|
||||
|
||||
|
||||
|
||||
## Applicability
|
||||
Use the Model-View-Controller pattern when
|
||||
|
||||
* You want to clearly separate the domain data from its user interface representation
|
||||
* Used in web applications to separate data model, user interface, and user input processing.
|
||||
* Suitable for applications where a clear separation of concerns is required, ensuring that the business logic, user interface, and user input are loosely coupled and independently managed.
|
||||
|
||||
## Tutorials
|
||||
|
||||
* [Spring Boot MVC](https://zetcode.com/springboot/model/)
|
||||
* [Spring MVC Tutorial](https://www.baeldung.com/spring-mvc-tutorial)
|
||||
|
||||
## Known Uses
|
||||
|
||||
* Frameworks like Spring MVC in Java for web applications.
|
||||
* Desktop applications in Java, such as those using Swing or JavaFX.
|
||||
|
||||
## Consequences
|
||||
|
||||
Benefits:
|
||||
|
||||
* Promotes organized code structure by separating concerns.
|
||||
* Facilitates parallel development of components.
|
||||
* Enhances testability due to decoupled nature.
|
||||
* Easier to manage and update individual parts without affecting others.
|
||||
|
||||
Trade-offs:
|
||||
|
||||
* Increased complexity in initially setting up the architecture.
|
||||
* Can lead to excessive boilerplate if not implemented correctly or for very small projects.
|
||||
|
||||
## Related Patterns
|
||||
|
||||
* [Observer](https://java-design-patterns.com/patterns/observer/): Often used in MVC where the view observes the model for changes; this is a fundamental relationship for updating the UI when the model state changes.
|
||||
* [Strategy](https://java-design-patterns.com/patterns/strategy/): Controllers may use different strategies for handling user input, related through the ability to switch strategies for user input processing.
|
||||
* [Composite](https://java-design-patterns.com/patterns/composite/): Views can be structured using the Composite Pattern to manage hierarchies of user interface components.
|
||||
|
||||
## Credits
|
||||
|
||||
* [Trygve Reenskaug - Model-view-controller](http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller)
|
||||
* [J2EE Design Patterns](https://www.amazon.com/gp/product/0596004273/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=0596004273&linkCode=as2&tag=javadesignpat-20&linkId=48d37c67fb3d845b802fa9b619ad8f31)
|
||||
* [Patterns of Enterprise Application Architecture](https://www.amazon.com/gp/product/0321127420/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=0321127420&linkCode=as2&tag=javadesignpat-20&linkId=d9f7d37b032ca6e96253562d075fcc4a)
|
||||
* [Head First Design Patterns: A Brain-Friendly Guide](https://www.amazon.com/gp/product/0596007124/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=0596007124&linkCode=as2&tag=javadesignpat-20&linkId=6b8b6eea86021af6c8e3cd3fc382cb5b)
|
||||
* [J2EE Design Patterns](https://www.amazon.com/gp/product/0596004273/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=0596004273&linkCode=as2&tag=javadesignpat-20&linkId=f27d2644fbe5026ea448791a8ad09c94)
|
||||
* [Design Patterns: Elements of Reusable Object-Oriented Software](https://amzn.to/3w0pvKI)
|
||||
* [Pro Spring 5: An In-Depth Guide to the Spring Framework and Its Tools](https://amzn.to/3y9Rrwp)
|
||||
* [Trygve Reenskaug - Model-view-controller](http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller)
|
||||
|
||||
Reference in New Issue
Block a user