ASP.Net MVC vs. HTML + KnockoutJS + WebAPI

Viewed 4868

I'm wondering why not just have static HTML files in an ASP.Net MVC 4 Web Project that use jQuery+jQuery Templates+KnockoutJS combination consuming REST based (ASP.Net MVC 4 WEB API hosted on Azure & secured using ACS). The Web API can use Entity Framework and return JSON serialized objects that can be retrieved using $.ajax() and bound using KnockoutJS.

What is it that ASP.Net MVC (for the Web pages) provides that adds value to this architecture?
On top of my head, I can think of:

  1. Multi device support (device detection and template replacement)
  2. Server-side validations of submitted data (not sure as I can also put the validations on WEB API?)
  3. I can still rewrite my URLs even if I'm using static html files (since I'm using ASP.Net MVC anyway).

Can someone help me understand this better? Thanks in advance.

5 Answers
Related