Asp.net 3.5 NTier Architecture

I am building a web application using asp.net 3.5, sql server 2008. My client wants it to be in minimum 3 tier architecture(Tiers are seperated physically, means 3 tiers means 3 seperate machines).

User Interface Tier: All the pages will be deployed on the different web server. This server will host only and only asp.net pages or server components.

Application Tier: This server will host the business logic and this is the tier where all the business logic will be implemented and deployed. This tier will fill the communication gap between database and the User Interface(UI).

Database Tier: A seperate server will be utilized to host the database only.

So far so good.

Actually my client is willing to use LLBLGen for the boiler plate code generation and to make the development fast.

My issue is that how can I call the components available at application layer from asp.net (user Interface layer)pages, because these application layer components are suppose to talk between the database and U开发者_Go百科I.

I have developed apps using the logical seperation where UI and BL is on the same machine. But on the different machines I am going to do it for the first time.

So please please kindly help me and if there is any good tutorial or article available kindly share it please.

Thanks and regards Shax

Since you didn't say anything about the type of application and the usage scenario (where you might need the security of multi-tier architecture) I wouldn't want to comment on whether the client needs such a thing or not. You might suggest to them that that sort of configuration will DECREASE performance if they think that that is the benefit of it.

I would recommend using the CSLA framework and then you won't have to worry about your deployment scenario. I have used it successfully for ages on many different projects and it will mitigate your architecture concerns and let you worry about providing real functionality.