Model–view–controller architecture

Model–view–controller architecture
Name	Model–view–controller
Title	Model–view–controller architecture
Genre	Software architecture

Model–view–controller architecture Model–view–controller architecture is a software architectural pattern that separates a software system into three interconnected components to decouple internal representations from user interaction. It is widely used in graphical user interface design, web applications, and interactive systems to organize code, improve maintainability, and support parallel development. Major technology organizations and academic institutions have influenced its adoption through frameworks, libraries, and curricula.

Overview

The pattern delineates responsibilities among distinct parts of an application to achieve separation of concerns and to facilitate testing, maintenance, and scalability. Prominent technology companies such as Microsoft, Apple Inc., Google, IBM and Oracle Corporation have shipped frameworks adopting this separation to support platforms like Windows, macOS, Android and iOS. Academic programs at institutions such as Massachusetts Institute of Technology, Stanford University, Carnegie Mellon University, University of California, Berkeley and University of Cambridge teach the pattern alongside system design topics such as Software engineering, Human–computer interaction, and Object-oriented programming. Industrial projects at firms including Facebook, Twitter, Amazon, Netflix, and LinkedIn often follow variants of the pattern in large-scale services and front-end engineering.

History and Evolution

Origins trace to early graphical systems and research groups that separated presentation from application logic. Early influences include work at Xerox PARC, implementations in systems from Sun Microsystems and design treatments in books by authors associated with Addison-Wesley and O’Reilly Media. The pattern was formalized and popularized through academic papers and conference presentations at venues like ACM SIGGRAPH, IEEE Computer Society, Association for Computing Machinery, and USENIX. Commercial frameworks such as Smalltalk, Ruby on Rails, Django, ASP.NET MVC, Spring Framework, and Angular evolved from community and corporate contributions, with influence from standards groups like World Wide Web Consortium and research funded by organizations including National Science Foundation and European Research Council.

Components (Model, View, Controller)

The Model encapsulates domain data and business rules and is analogous to components used in systems designed by companies like SAP SE and Salesforce. Models integrate with persistence layers from vendors such as Oracle Corporation, Microsoft SQL Server, PostgreSQL, MongoDB, and MySQL. The View renders information to users and often relies on rendering engines or toolkits provided by KDE, GNOME Project, Qt, GTK, and browser engines developed by Mozilla Foundation and Chromium. The Controller handles input and mediates between Model and View; controller logic appears in libraries maintained by organizations like The Apache Software Foundation, Ruby Central, Python Software Foundation, and Eclipse Foundation. Patterns in this component trio are taught at Princeton University, California Institute of Technology, and used in products from Adobe Inc., Autodesk, Siemens, and Intel Corporation.

Variations and Related Patterns

Numerous derivatives and related patterns exist, reflecting different trade-offs. Variants include Model–view–presenter (MVP), Model–view–viewmodel (MVVM), Presentation–Abstraction–Control (PAC), and Layered architecture as used in projects by Microsoft Research and research groups at Bell Labs. Reactive and dataflow approaches from companies like ReactiveX, Facebook (with concepts introduced in React), and academic work at Massachusetts Institute of Technology spawned hybrid patterns integrating unidirectional data flow. Enterprise patterns cataloged by Martin Fowler, Eric Evans, and groups associated with Pattern Languages of Programs influenced middleware and integration approaches used by Red Hat and Canonical.

Implementation and Examples

Implementations span programming languages and platforms. Web frameworks such as Ruby on Rails, Django, ASP.NET MVC, Spring Framework, Laravel, and Symfony provide MVC-orientated scaffolding. Desktop toolkits like Qt, GTK, JavaFX, and Swing implement MVC-like separations in GUI applications used in products from Siemens, Nokia, Motorola, and Lenovo. Mobile SDKs by Apple Inc. (UIKit), Google (Android SDK), and cross-platform tools from Xamarin, React Native, and Flutter reflect MVC influences. Large-scale services at Amazon, Netflix, eBay, PayPal, and Alibaba Group use adapted forms to organize front-end and back-end interactions, integrating components like REST, GraphQL, and message brokers such as Apache Kafka.

Criticism and Limitations

Critiques address ambiguity in component boundaries and suitability for modern asynchronous, component-based, or single-page application paradigms. Commentators from ACM and practitioners at Google and Facebook note that MVC can lead to "fat controllers" or "anemic models" without disciplined conventions. Alternative approaches promoted in books from O’Reilly Media and white papers by Gartner and Forrester Research emphasize patterns like MVVM, Flux, and microservices for scalability and maintainability in distributed systems. Regulatory and compliance contexts involving organizations such as European Commission or U.S. Department of Commerce may impose data-handling constraints that complicate straightforward MVC deployments.

Category:Software architecture