Are there any negative reasons to use an N-Tier solution? *

Question

I'm pretty new to my company (2 weeks) and we're starting a new platform for our system using .NET 3.5 Team Foundation from DotNetNuke. Our "architect" is suggesting we use one class project. Of course, I chime back with a "3-tier" architecture (Business, Data, Web class projects).

Is there any disadvantages to using this architecture? Pro's would be separation of code from data, keeping class objects away from your code, etc.

Answer

I guess a fairly big downside is that the extra volume of code that you have to write, manage and maintain for a small project may just be overkill.

It's all down to what's appropriate for the size of the project, the expected life of the final project and the budget! Sometimes, whilst doing things 'properly' is appealing, doing something a little more 'lightweight' can be the right commercial decision!

< br > via < a class="StackLink" href=" http://stackoverflow.com/questions/5880/" >Are there any negative reasons to use an N-Tier solution?< /a>

Share on Google Plus

About Cinema Guy

This is a short description in the author block about the author. You edit it by entering text in the "Biographical Info" field in the user admin panel.