liveBook · Manning

Model–view–controller

Model–view–controller is an architectural pattern that separates application data and behavior, presentation, and interaction handling into model, view, and controller responsibilities.

How 4 Manning books explain it

ASP.NET Core in Action, 3e

Model-View-Controller is an application architecture pattern that separates domain data, presentation, and request-handling control logic.

How it is used
Structures user-interface requests by separating business data, request handling, and presentation in Razor Pages, MVC controllers, and web APIs.
How deep it goes
Defines each role and walks through a Razor Page request, then relates the pattern to controllers and APIs.
Examples
Uses a to-do category page whose OnGet handler calls ToDoService and passes items to a Razor view.
What you can do after
Apply it via Razor Pages to keep request coordination, business logic, and HTML generation in separate components.

Read how ASP.NET Core in Action, 3e explains Model–view–controller →

Web Components in Action

An application architecture pattern that separates model data and business logic, view presentation, and controller input handling into distinct responsibilities.

How it is used
Organizes web-application data flow by separating presentation, interaction logic, and application data.
How deep it goes
Defines the three roles and demonstrates their coordination through Web Components, event listeners, and data-model methods.
Examples
Uses an exercise library, workout plans, localStorage persistence, templates, and click or change listeners.
What you can do after
Apply it to move exercise and workout-plan data out of rendering components into reusable model interfaces.

Read how Web Components in Action explains Model–view–controller →

Pro ASP.NET Core 7, Tenth Edition

MVC is an architectural pattern that separates an application into models, views, and controllers.

How it is used
Structures ASP.NET Core applications by separating models, views, and controllers, while supporting controller-based web services.
How deep it goes
Defines separation of concerns and controller usage, but stops short of detailing Razor view implementation.
Examples
Uses controller-defined web services and MVC controllers with views for core data operations.
What you can do after
Apply it via ASP.NET Core controllers, models, and views to structure web services and form applications.

Read how Pro ASP.NET Core 7, Tenth Edition explains Model–view–controller →

Django in Action

Model–view–controller is an architectural pattern that separates an application into data and business logic, presentation, and interaction-control components.

How it is used
Frames dynamic web applications by separating stored data, presentation, and user interaction.
How deep it goes
Defines the three MVC roles and traces Django URL dispatch, but leaves the view-controller boundary intentionally unresolved.
Examples
Uses Django’s urls.py, urlpatterns, request objects, view functions or classes, response documents, and template rendering.
What you can do after
Evaluate/understand how a Django URL becomes a rendered response through routing and a view.

Read how Django in Action explains Model–view–controller →

Related concepts

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.