[2005] ASP.NET 3 tier application

[usamaalam]

Hello everybody,

I am designing a web application in 3 tiers with one separate class library project for DataAccessLayer, one separate class library project for BusinessLogicLayer and ASP.NET website. I am planning to deploy all these three projects on different servers.

How should I expose my methods in DAL and BLL and what design considerations I should make so that I will be able to access DAL methods from BLL and BLL methods from website each on separate server?

Thanks.

[mendhak]

You're going to place the DLLs on separate servers? Why? I'd think that's your first design consideration. Answering that question. Why would you do that? If you need to, why not use a web service?

[usamaalam]

Thinking to put different layers on different servers because too much traffic is expected on the site. I am on the initial phase of the design so just looking for design alternatives.

Thanks.

[Kasracer]

Thinking to put different layers on different servers because too much traffic is expected on the site. I am on the initial phase of the design so just looking for design alternatives.

You're looking at these objects like you would an image the user has to load. These things are not being sent to the client so the impact of high traffic should be minimal to the amount of layers you have. In fact, spreading the layers across multiple servers would probably slow your site down incredibly as you would constantly connect to each layer for every page view.

Go for the typical
DAL -> Database
BLL -> DAL
Site -> BLL

There are plenty of articles out there if you want to review what others have done architecture wise. Just implement what makes sense. Don't handle any SqlParameters in your BLL and don't create any logic in your DAL other than fetching or sending data that the BLL can request.