Last post Jan 12, 2010 02:45 AM by atconway
Jan 07, 2010 06:39 PM|bihariagrawal|LINK
Can any one explain 3 layer Architecture (in detail) with example.
Jan 07, 2010 07:26 PM|Yousef_Jadallah|LINK
The best reference that I read in this issue and I profit from it, you can find here in this link
Jan 07, 2010 07:43 PM|mohammed askar|LINK
Jan 07, 2010 08:55 PM|mxmissile|LINK
Jan 11, 2010 12:28 PM|dinesh.gouttam|LINK
Check this link http://weblogs.asp.net/saurabhnijhawan/archive/2009/10/06/creating-a-n-3-tier-layered-application.aspx
Hope this will helps you.
Jan 12, 2010 02:45 AM|atconway|LINK
To start with some good reading that includes details, read over the following articles which gives a good overview of building a n-tier application with the UI->BLL->DAL (3-tier) implementation:
Building an N-Tier Application in .NET:
3-tier Architecture with ASP.NET (choose language on link screen, then proceed):
As some additional helpful information, you should also understand is the difference between an n-tier 'logical' structure and an n-tier 'physical' structure.
An n-tier logical structure is the number of individual logical
layers within your architecture. In your case the UI, BLL, and DAL are all
logically separated into their own tiers and have their own responsibilities.
An n-tier physical structure is the number of physical different tiers or typically servers in which the logical tiers are separated by. You could have a 'SmartClient' application that may completely reside on the client (including the
datasource in some scenarios) thus residing on a single tier, but the logical architecture is still an n-tier design with multiple logical layers.
Typically an n-tier logical design using common tiers like the UI, BLL, DAL offer a nice separation of concerns and scalable design. So separating logical tiers is always something I recommend. However, separating tiers or components into separate physical
tiers is something that should only be done when required or needed. Why? Well the more physical tiers, the more network hops that will be introduced, and ultimately there will be performance considerations.
If you would like to read a great explination about this more in depth take a look at Chapter 1 in the book by Rocky Lhotka titled:
Expert VB 2005 Business Objects (http://books.google.com/books?id=AS7zAQaKt-oC&dq=rocky+lhotka+Expert+2005+Business+Objects+vb.net&printsec=frontcover&source=bn&hl=en&ei=8OMoS9yjIs2vtgfv0oTRCw&sa=X&
Hope this helps get you started!