Add a comment

 

Re: When do you need a 3-tier architecture?

Two circumstances when I always set up a separate app tier are when using Smart Clients and for SharePoint web parts (my personal preference is to minimize what's deployed to the SP web front end boxes). For "normal" ASP.Net sites I go with 2 tiers (of course, if I make use of a service external to my app, that increments the tier count). By using a chunky, message based design for my business layer I can switch if needed from 2 to 3 tier merely by adding some config entries and swapping the proxy that the presentation layer uses (one for "direct " access, another for via a service layer).

Re: When do you need a 3-tier architecture?


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).