N-tier

  • Thread starter Thread starter p988
  • Start date Start date
P

p988

If I have a web app which provides interface to customers for ordering items
of goods through IE browsers. The interface is built on ASP.NET. The
interface calling bunch of DLLs and the DLLs in turn link to a database on a
SQL server.

Should this be regarded as 3 tiers or 2 tiers?

Is there any synchronization issues involved here, like inside DLL and
accessing database if many customers access the same ASP page?

Thanks in advance!
 
Hi p988,

This would be a three tier application:
Database <=> Data Access / Business Logic <=> Web Interface

You may want to consider using caching if you are concerned about a slow
load time with a lot of hits.

As far as synchronization, you'll need to elaborate and explain what you
mean by that.

Alex Papadimoulis
 
A typical architecture looks like this-
1. Front End (ASPX Pages)
2. Middle Tier (Web Services) + Data Acess Layer.
3. SQL Server.

Tiers are not directly proportional to dll's used.
An segment of an application is called a tier if you can have that segment
in a seperate machine.
In some situations I have had all three tiers in the same machine or in
others three different machines.
cheers
jay
 
Back
Top