Application model
An application model is a structured representation of an application’s data, concepts, components, relationships, or runtime state.
ASP.NET Core in Action, 3e
An application model is an architectural component that encapsulates the non-user-interface parts of an application, including domain models, services, and data-access interactions.
- How it is used
- Handles state and business logic behind responses while page handlers coordinate requests and views generate HTML.
- How deep it goes
- Defines an architectural boundary and traces its role through a request, without specifying how to implement its services or database access.
- Examples
- Uses a to-do category request involving permission checks, item searches, database loading, and a page-handler response.
- What you can do after
- Evaluate/understand where business logic belongs when separating Razor Page handlers, views, and request data.
Read how ASP.NET Core in Action, 3e explains application model →
Spring in Action, Sixth Edition
Model is a Spring MVC object that carries attributes from a controller to a view.
- How it is used
- Carries controller attributes to a Spring MVC view during request handling.
- How deep it goes
- Explains population with an object and rendering through a logical view name.
- Examples
- Uses a /design request, an empty Taco attribute, the taco key, and the taco logical view.
- What you can do after
- Apply it via Spring MVC to pass form data from a controller to a rendered view.
Read how Spring in Action, Sixth Edition explains application model →
Related concepts
- handlerused by · A handler is a callable or software component that processes an event, request, message, or other input and performs associated processing.
- Model–view–controllerpart of · Model–view–controller is an architectural pattern that separates application data and behavior, presentation, and interaction handling into model, view, and controller responsibilities.
- Aspireused by · Aspire is a .NET cloud-native application framework for modeling, running, configuring, and observing distributed applications during development.
- domain modelhas part · A domain model is a software representation of the concepts, entities, relationships, rules, and behavior of a problem or business domain.
- business logichas part · Business logic is the domain-specific rules, computations, and decisions that determine how a software system behaves and processes operations.
- servicehas part · A service is a software or computing capability that provides defined functionality to users or other components through an interaction boundary.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.