CODEWITHSUNDEEP
ajaxasp.net-mvc-3web-serviceshtml
zu1b
zu1b

Reputation: 587

html5 and webservices versus mvc3

At my company we have a discussion as to in what way our future web applications should be build. We currently have 2 groups of developers who agree on several things. We all want to use html5 and css3 and jQuery. We mostly agree that web services will be very important.

However, one group advocates the use of mvc because it would add more structure? to the project. The other half (to which I admit I belong to), sees no reason not to consume the webservices directly from the client, forgoing mvc controller views etc.

To me adding mvc will only add another performance burden on the server that could be shifted to the client and structure could also be added to non mvc projects, though it might ask a little more effort from the developers.

At the risk of starting a flamewar. I would like to hear some arguments for either side from outside the company.

Upvotes: 0

Views: 244

Answers (1)

ZippyV
ZippyV

Reputation: 13018

You are having the wrong discussion. HTML5, CSS and Javascript (and JQuery) are client side technologies. ASP.NET MVC is a server side technology. You still need code on the server that sends and retrieves data from the database. The next version of MVC (4, beta) will have Web API which is an excellent solution to create those webservices with.

Upvotes: 1

Related Questions