Re: Help on n-Tier architecture ???

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hello serge,

Take into account that there are two concepts - "tier" and "layer"
Tier is a physical location and layer is abstract location. Tiers located on different machines and liers could locate on one.
Advance of n-tier architecture is to give scalability, reliability and durability, and it's not important that all layers/tiers should be physically distributed


In general, in small apps, the tier-layer-layer is most common solution. It means that smart-client locates on separate machine and business and data layers on the second one. In your scenario B and C componens could locate together.
To move divide the on different machines only thing u should undertake is to create proxy from component C and use it with your B component.
It's a couple of clicks in Component Explorer


sc> I am studying an application architecture based on an n.Tiers
sc> architecture. I have it defined as:
sc> Presenation tiers
sc> Buisness logic
sc> DataLayer
sc> Actually as far as I have understand benefits of 3 or N-tiers
sc> architecture, excpet all adavntage of code maintenance and
sc> scalability, they shoud be able to be installed separatly on
sc> different machine rignt ?
sc> sc> In that case let say that my Presnetaion layer is my Internet
sc> browser from a computer A. Then my buisness logic is installed on a
sc> computer B (Web Server) and Datalayer is on Computer C (SQL server
sc> DB).
sc> sc> On computer C I have a class library which is in charge to connect
sc> to the
sc> database
sc> From computer B my application need a reference to the class library
sc> of
sc> computer C.
sc> How all this reference is done ?
sc> sc> thnaks for your reply
sc> regards
sc> serge
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/members/laflour


"At times one remains faithful to a cause only because its opponents do not cease to be insipid." (c) Friedrich Nietzsche


.



Relevant Pages

  • Re: OBJECT-ORIENTED LAYERED ARCHITECTURE AND SUBSYSTEMS
    ... > OBJECT-ORIENTED LAYERED ARCHITECTURE AND SUBSYSTEMS ... > requirements of system owners, users, and clients. ... > code modules which all carry out the same necessary tasks for a layer. ... > each of those areas, or domains, constitutes a subsystem. ...
    (comp.object)
  • OBJECT-ORIENTED LAYERED ARCHITECTURE AND SUBSYSTEMS
    ... OBJECT-ORIENTED LAYERED ARCHITECTURE AND SUBSYSTEMS ... project's physical design, and implementation. ... code modules which all carry out the same necessary tasks for a layer. ... each of those areas, or domains, constitutes a subsystem. ...
    (comp.object)
  • Re: hi QUESTION
    ... Do you even understand "Architecture" of computers. ... This architecture in particular is the Processor of the HP-UX machines ... This is the Itanium version of Debian Linux. ...
    (Debian-User)
  • [opensuse] Re: [opensuse-ppc] No More Official PPC Distro
    ... amount of worth out of older machines would also benefit. ... Today's world is one where the x86 architecture is not absolutely ... Michael Loeffler about why there wasn't a PPC version of 11.2: ... an openSUSE ppc distribution." ...
    (SuSE)
  • Re: Some architecture advice
    ... > I've used business objects for a while, ... > make apps that are more maintainable. ... each layer is independent of one another and each ... > Being relatively inexperienced with architecture I'm sure ...
    (microsoft.public.dotnet.framework.aspnet)