Problem wth separation technique of 3layer architecture

Question

Hi...

I'm trying to make a program using 3 layer architecture, but I have a problem with how I separate the layers. I was try to search in google but still don't understand. If I separate the layers in different project but still in one solution, is it called 3 layer or 3 tier architecture?

Can soemone give me an explanation maybe, or reference about the difference separation technique in 3 layer and 3 tier architecture?

Thank you...

Amit Choudhary · Answer

First you should understand the layered and tiered architecture. Layered is when you separate your code based on the purpose of the operation the layer is doing. This keep your code maintainable. You can easily identify your components based on their naming convention. for e.g. Project.DataBaseAccess is containing only the database operation. while your Project.UI contains all the UI elements and everything related to and UI. So you have everything in a separate layer. Tiered is basically next to Layered. You have created Layered architecture but You'll not use direct references of the project but you'll create a communication channel to provide the interaction between them. For e.g. you have the Database Access layer and the UI Layer then if you expose the Data Access operation Via a service like WCF Webservices etc. then This will be called as Tiered Architecture. I've also wrote a blog on the same. Have a loook. Though it's only theory based. http://www.cshandler.com/2011/07/difference-between-layer-and-tier.html H ope you understand the difference and benefits of using these.