ASP.NET MVC vs. Webforms vs. HTTP Handlers (.ashx)

Question

I plan on building a simple, yet high usage webapp and need to settle on an architecture.

• basic server side logic / dynamic db driven content about half a dozen to a dozen pages serving up all said content
• no need for URL rewriting,
• pretty simple page flow/routing

The objective is to publish this app to use the least amount of bandwidth, memory, and CPU as possible. That said, my options are to

1. build in ASP.NET MVC

2. build in webforms with viewstate disabled

3. build using .ashx handlers with code that concatenates all HTML output into strings that it spits out

Which is the most lightweight solution?

I appreciate the responses so far, but i'm not asking for the best solution. This is a simple app, and i want the solution that will use the fewest machine/network resources.

Answer 1

You should use MVC, because you have a lot of more control about the generated client code than in WebForms, and is simpler than ashx handlers.

Answer 2

ASP.NET MVC, Web Forms and the Generic Handler (.ashx) are all HttpHandlers implementing the IHttpHandler interface.

Out of these options the Generic Handler (.ashx) would be the most lightweight.

Answer 3

WebForms are going to be the heaviest in most cases. ASP.Net MVC is quite lightweight and surprisingly fast compared to WebForms.

Building an application using HttpHandlers to serve pages may be fast when serving static content, but if you plan to use some sort of templating to serve dynamic data, you're going to cause yourself a lot of undue work. As for performance, it's hard to say with this option because your templating could be nasty or possibly not.

Answer 4

ASp.NET MVC is as close as you can get to HtTP and Html.

Answer 5

HttpHandlers are the most light weight, because the interface behind the ASHX file is IHttpHandler which is the basis of the Page object that is used both for Web Forms and MVC.

Answer 6

HttpHandlers are the most lightweight from your list of 3 options.

Personally, I would use ASP.NET MVC because it gives you a richer development environment with very little extra server overhead, especially if u turn most things off ..

eg. roles, etc.

Also use IIS7 intergrated mode and turn as much IIS7 settings off etc.