Last post Apr 04, 2009 06:16 PM by ArminStockner
Apr 02, 2009 02:27 PM|Tulsim83|LINK
Apr 02, 2009 04:15 PM|ArminStockner|LINK
Take a look at this. This is the very best article I have ever read about this topic.
I am glad to hear your feedback
Apr 03, 2009 03:01 PM|Tulsim83|LINK
Thanks for the article link.
I've briefly read through some pieces of the article and it definitely seems very like a very good description. However, it seems like a lot of added work which I can imagine would probably make sense for larger applications. But what about smaller applications?
Do you think all the added work is justified? When does it make sense to incorporate n-tiered design in an application?
Apr 04, 2009 06:16 PM|ArminStockner|LINK
Well this is not easy to say. So if you have just a couple of pages which are displaying some content with few code behind you can do it without BLL and DAL.
You should use n-tier-architecture if your code does change alot. Or you make a lot of enhancements in your projects. So n-tier-architecture improves your flexibility and changeability of your website.
And think about what is if your page will grow?
So keep in mind if you change or enhance a lot do it with n-tier