To MVC or not to MVC?

by George 25. December 2008 14:27
I have been following ASP.NET MVC ever since it was brought up as the meta-pattern behind Stackoverflow.  As I referred to in my last post, I'm in the process of building a website for a local Catholic school.  Part of the the act of building the site is determining whether or not I want to go the extra mile and really make it something special, or if I just want to 'make it work'.  The traditional Web Forms + NHibernate + SQL Server will make it quite easy to build; but then I wouldn't be learning anything new.  MVC does seem like overkill for the task at hand, however.  So the question at hand, Speed? Or doing it the right way?

Tags: , ,

Comments (5) -

Daniel Rosenstark
Daniel Rosenstark
12/27/2008 5:48:26 PM #

MVC is never overkill. Some MVC frameworks might be overkill (I don't know ASP.NET's MVC framework) to implement, but at some point you will have to get friendly with an MVC framework for your technology stack. If not ASP.NET MVC, then choose something else and go with it.

Well, those are my two cents.

Reply

Cal Jacobson
Cal Jacobson
2/10/2009 4:06:27 AM #

I know I'm late to this discussion, but I think it depends on a) if the functionality of the site could grow in the future and b) if you'll be maintaining it.  If the answer to either is "yes" then I'd say stick with the MVC approach.

Reply

Shawny
Shawny
5/20/2009 1:44:41 PM #

MVC/MVCS (Model, View, Control, Service) is basically just an approach to solving a problem/set of problems.  I have played briefly with .Net's MVC but have a vast history with Cairngorm, and there are times where MVC/MVCS can be overkill.  As an academic exercise, I would say go for it.  Seems that there is a large following of the pattern in the industry right now and you can never have too much experience... except in cases of sunburn.

Reply

Daniel Rosenstark
Daniel Rosenstark
5/20/2009 10:07:53 PM #

I've been forced to use Rails (with Ruby) for the last 4 or so months, and I have to say that it's NEVER overkill, even to do a one-page site. It just gives you some way to organize the pieces, which are ALWAYS the same: models, views, and controllers. While I do hate dynamic languages and Ruby in particular for its absurd flexibility (from what I've heard of Python it sounds a lot more interesting), Rails has made me understand that certain core patterns -- MVC in particular -- are ALWAYS worth using.

Reply

Lamar Spallone
Lamar Spallone United States
3/26/2012 2:08:33 AM #

Sometimes I contemplate if folks truly take time to publish something original, or are they only just dishing out words to fill a site. This surely doesn't fit that mold. Thank you for taking the time to write with awareness. From Time To Time I look at a page and question whether they even proofread it.Fantastic work with this article.

Reply

Add comment

  Country flag

biuquote
  • Comment
  • Preview
Loading

Me!

This space intentionally left blank.

Month List

Page List