To begin our programing journey, we are going to start at the foundation of most modern languages frameworks are being used upon. The MVC architecture! In this first lesson, we are going to try to keep it short and sweet by only going into a somewhat broad overview, saving the detailed explanation for the second part of this post.


What does MVC stand for?


MVC stands for Model View  Controller. Models are where the real coding in whatever language you’re using takes place. This is where all the functionality will be that interacts with the database. Views are the files that use front-end code(HTML, CSS, etc) to present themselves to web browsers. Controllers act as a bridge between the two because the controller will take what needs to be displayed to the view from the model and make it accesible there. The ideal relationship between models and views are having a fat model and skinny controller.


Popular users of the MVC architecture


  • Ruby on Rails
  • CakePHP
  • Codeignighter
  • Backbone.js
  • Node.js


What’s to come in part 2


In the second installment of this blog post, we are going to take a more in depth look by viewing various code examples, going over the actual interaction process for the MVC framework, and a little bit more on the history.