The MVC Design Pattern On Web Applications
Originally written in May 2007 for a technology blog called CFGigolo.com (which used to be a Google Page Rank 7), this article described my vision for improved web application in both terms of interface and reach. At that time I was on a great team developing corporate web application. A lot happened since: more capable smartphone, evolution of web programming languages, the boom of mobile and so on. I’m glad the world evolved more than my vision were able to capture at that moment. I hope we continue to execute and evolve more than our mind limits.
There’s a lot of talking on “MVC” on software development. People starting developing web applications or “Rich Internet Application” talk about that too. Several web development frameworks allow or require it, therefore there’s even more discussion about it.
The way to understand the MVC architecture (I find more descriptive calling it an architecture instead of a framework or paradigm) is the same to understand any design pattern:
which problem it solves (the motivation behind this pattern)
understand the pattern
understand how this specific pattern solves our recurrent problem
Increased Complexity, Need to Decouple
MVC and Three-Tier Architecture: Scope and Flow
The Three Monkeys and the MVC
The View is voiceless but it does gestures (user gestures!) to the Controller and listen for Model changes.
This was a great analogy, and we used that for a long time to grow our team.