3 Tier architecture

  • Thread starter Thread starter Dan, Vascas
  • Start date Start date
D

Dan, Vascas

Please clear my doubt and give some suggestion.
I am new to software development, and want to implement a n-tier
application.
I have a very basic idea about n-tier architecture.

[Example]
I have created a Business Layer(dll) and put it on a network shared
directory.
From the presentation layer project I have added the reference of Business
Layer(dll).

Can I call this a n-tier application.
Or n-tier means that I need to execute/process the Business Layer where it
presents(using remoting or any other way).

Please clear my doubt.

Thanks for any help you can provide.
Dan
 
n-tier is ambiguous imo, but its usual definition refers to partitioning
your application into multiple physical tiers (think distributed
application). This could be as simple as a winform client, with a
database server, and some of the logic being leveraged from web services
on one or more web servers. You could take it a step further by saying
for instance that security services are provided by your active directory.

I think that what you are describing is better referred to as a layered
application, which can be achieved without involving other "tiers".

Regards,

John Parrish
 
Thus wrote Vascas,
Please clear my doubt and give some suggestion.
I am new to software development, and want to implement a n-tier
application.
I have a very basic idea about n-tier architecture.
[Example]
I have created a Business Layer(dll) and put it on a network shared
directory.
From the presentation layer project I have added the reference of
Business
Layer(dll).
Can I call this a n-tier application.
Or n-tier means that I need to execute/process the Business Layer
where it
presents(using remoting or any other way).
Please clear my doubt.
Click to expand...

Tiers refer to physical processing nodes. Your application is probably 3
layered (which is good), but not 3 tiered (which doesn't mean it's bad).

Cheers,
 
Back
Top