title: ASP.Net MVC VS Javascript UI
body: <p>I haven't done any web development for the last 6 years apart from a small silverlight project two years ago.
  So 6 years ago I was working on a web project project using ASP.net and I must confess that I never liked Web Forms. Because ASP.Net
  was a requirement I and because I was starting to get interested in Restfull web services, I used markup free ASP.Net pages,
  each being a controller, and in each there was a big if, which was looking for the method name in xml message being sent from the front-end.
  Around that time I started seeing web application using web services for the back-end and javascript only interfaces, which were using Ajax requests.</p>
  
  <p>So for the last 6 years I´ve worked mainly in the Services Layers, with SOA and more recently with Event SOA, so to me I don´t understand the need for ASP.Net MVC,
  I am learning it, because it seems to be a requirement everywhere this days, but in the times of SOA why do you need ASP.MVC if you are using just MSFT stack?</p>
  
  <p>Say I want to build a new system, with a web front-end, and I built it in Layers, like the example bellow:</p>
  
  <p>DAL -> SOA Services -> Web API (WCF) -> Front-End (JavaScript only)</p>
  
  <p>Would it be better if a built it using ASP.NET MVC? I mean don't take me wrong but I just don´t see it fit anything but small non-layered projects.</p>
  
  <p>ASP.Net MVC is a huge improvement over Web Forms, and I was hoping you guys could give me some insights on this; I am not trying to be cynical here, I've been
  away from Web Developmental for a long, time and I just need to know why people seem to prefer ASP.Net MVC over plain JavaScript front-ends.</p>
  
  <p>Thanks a lot.</p>