Model Structure in MVC

In MVC, the model layer is not a single class or object but rather comprises three primary elements:

• Domain Objects: Encapsulate pure domain logic - business rules and concepts, independent of storage mechanisms.
• Data Mappers: Translate data between domain objects and a specific storage medium (e.g., database, file system).
• Services: Orchestrate interactions between domain objects and data mappers, providing a public interface for accessing the domain logic.

Separation of Concerns

A clear separation between the model layer and other components is crucial for adhering to the single responsibility principle, providing flexibility, keeping controllers simple, and facilitating future API development.

Accessing the Model

Controllers and views can access services through:

• Direct injection via dependency injection (preferred)
• Using a factory that provides mandatory access to services

Changing Model State

Controllers modify model state by interacting with services. They do not validate user input or perform direct database queries.

Presentation of Model State

Views determine the response output (e.g., redirecting to a different page, rendering a specific template) based on the current model state.

REST APIs

In REST APIs, the presentation layer simplifies significantly, allowing a more direct connection between service methods and response generation. However, complex presentation logic can still warrant a separate view layer.

Building the Model

Instead of creating a single "Model" class, developers define services, domain objects, and data mappers based on the required functionality.

Additional Considerations

• Database Tables and Model: Not always a direct 1:1:1 relationship, as domain objects may span multiple tables or share common operations.
• Views and Templates: Views handle presentation logic and select appropriate templates based on data received from the model layer.
• View and Controller Relationship: In website MVC implementations, each view typically has a dedicated controller for handling requests related to that particular page.
• MVC Variation: MVP is a variation of MVC where views and controllers share responsibilities, simplifying view development.