Model–view–controller
Model–view–controller is a software architectural pattern that separates application data and behavior, presentation, and interaction handling into model, view, and controller responsibilities.
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
- Uses MVC to organize server-rendered pages and web API request handling.
- How deep it goes
- Explains component responsibilities and request flow, then traces their application to Razor Pages and controllers.
- Examples
- Traces a to-do category page and compares a grocery application’s HTML and API requests.
- What you can do after
- Apply it via ASP.NET Core Razor Pages by separating request handling, application logic, and HTML generation.
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 →
Test Driven: Practical TDD and Acceptance TDD for Java Developers
Model-view-controller is an architectural pattern that separates an application into model, view, and controller components.
- How it is used
- Organizes user-facing application components by separating domain logic, presentation, and interaction handling.
- How deep it goes
- Defines component responsibilities, traces a web request, and notes Swing’s merged view and controller.
- Examples
- Uses a web request for a list of U.S.-built cars and Swing widgets operated to simulate user input.
- What you can do after
- Understand how MVC assigns responsibilities and moves data through a web request.
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.
Also covered in
- Kafka Streams in Action, Second Edition
- Simple Object-Oriented Design: Create clean, maintainable applications
- Grokking Web Application Security
What to know first
- ASP.NET Web FormsASP.NET Web Forms is a Microsoft server-side web application framework based on page-oriented development, server controls, and event-driven programming.
- web applicationA web application is software that provides functionality through web technologies and is accessed over a network, typically through a browser or other web client.
- design patternA design pattern is a reusable, general solution structure for a recurring software design problem.
- HTMLHTML is the standard markup language for structuring content and elements in documents on the web.
Related concepts
- controllerhas part · A controller is a software component that receives input or requests and coordinates other components or operations to produce a response or change application state.
- design patternkind of · A design pattern is a reusable, general solution structure for a recurring software design problem.
- viewhas part · A view is a representation or access interface that presents selected, transformed, or derived information from underlying data or state.
- software architecturekind of · Software architecture is the significant structure of a software system, including its components, relationships, and design decisions that shape how the system is built and behaves.
- MVC modelhas part · An MVC model is the application component that represents application data and associated domain logic, making relevant state and behavior available to other components such as views.
Questions about Model–view–controller
What is Model–view–controller?
Model–view–controller is a software architectural pattern that separates application data and behavior, presentation, and interaction handling into model, view, and controller responsibilities.
Which Manning books explain Model–view–controller?
ASP.NET Core in Action, 3e, Web Components in Action, Test Driven: Practical TDD and Acceptance TDD for Java Developers, Pro ASP.NET Core 7, Tenth Edition and Django in Action.
What should I know before learning Model–view–controller?
Manning books that teach Model–view–controller usually introduce ASP.NET Web Forms, web application, design pattern and HTML first.
What is Model–view–controller a kind of?
Model–view–controller is a kind of design pattern. A design pattern is a reusable, general solution structure for a recurring software design problem.
What are the parts of Model–view–controller?
Model–view–controller includes controller, view, model and MVC model.
What is Model–view–controller also called?
Model–view–controller is also called MVC.
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.




