N-Tier application??

[Pablo]

My application uses a class to access to the dataBase, there are several
ones who are bussines objects (and uses the first one to work with the
database) and, finally, I have the interface objects.
Actually, I don't have any sql embebbed in the code so I'm working with
stores procedures in SQL Server.

Can I say that this is a n-tier (4 in this case) application?

Thank you very much.

 

[Guest]

My application uses a class to access to the dataBase, there are several
ones who are bussines objects (and uses the first one to work with the
database) and, finally, I have the interface objects.
Actually, I don't have any sql embebbed in the code so I'm working with
stores procedures in SQL Server.

Can I say that this is a n-tier (4 in this case) application?

Thank you very much.

In my opinion, I would call this a classic 3-tier (or n-tier) architecture.

The interface is a tier, the business objects are a tier, and the database
(server + stored procedures) is a tier.

I would consider the database object itself more of a facade over the data
tier, simply hiding the database details from the business objects.

The database object would most likely be deployed with the business objects
(tightly coupled) whereas the calls from the database object to the database
stored procedures would most likely be across a machine/process boundary
(loosely coupled).

One significant advantage of the n-tier (2 or more tiers) is the flexibility
to deploy the various tiers on separate machines to add horsepower where you
need it most, be that the database, the business, or the interface tier.

Hope this helps,
-james

 

[Lloyd Dupont]

it's a 2 tiers!

what's tier?
it's (roughly) a process in your application.

for example client (1 process on the client computer), communicating to your
server (a process on your server) to do some operation and query the
database (an other process), that's 3 tier

web app are three tiere too: the browser, your server, the database