The Model View Controller (MVC) [[Code Design Patterns|pattern]] is an application development pattern in which an underlying data model & the visible aspects are separated, only interacting via an intermediary component called the Controller.[^1] ![[Pasted image 20240820205050.png|From the source]] The MVC pattern rocks. It's a good way to handle [[Separation of Concerns]], keeping [[Coupling]] to a minimum. It's a form of [[Model-View Separation]] that works for applications with user interfaces. [[React]] is built around this concept, where the data model can be focused on and the view *reacts* via the react code + their own code, which collectively is the *controller*. **** # More ## Source - Self, at this point. - https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-model-view-control-mvc/ ## Related [^1]: Although this was called the "Octopus" back when I first learned it.