title: Does having multiple web front ends and a single database back end fit into the MVC design pattern?
body: <p>We have 3 websites at the moment that all operate off the same database backend and they share almost 100% of the business logic.</p>
  
  <p>It is becoming a pain to have to update 3 website's code every time to accommodate a small change. Would using ASP.Net MVC work for us?</p>
  
  <p>What I am thinking is the business logic and database is almost identical in all 3 so extract that away into the Model and the Control. Then each web front end (which looks different) each has a different View. It would then be Nice to have a single project where we can have all the code for the Model and Control shared. And 3 different views. </p>
  
  <p>How would we deploy something like this? Share a single codebase for Model and Control and have 3 separate URLs using 3 different Views. Or is there a better way to do this? </p>