Architecture question ?

[serge calderara]

Dear all,

SO far I was doing only single windows desktop application
Now I have in front of the fact that some of my customer project demand are
talking about having or using a 3 tier or 2tier component architecture ...

What does this really means in real word, with real words ????

thnaks for your help

regards
Serge

[Morten Wennevik]

Re: Architecture question ?

Hi Serge,

It means instead of having a single executable, you split it into
parts/layers that communicate with eachother, and may be individually
upgraded when needed. A 3-tier solution often means, one part is doing
the User Interaction, displaying and retrieving data to/from the user,
another part doing the data processing (often called the business logic
layer) and a third doing database storage and retrieval.
2-tier usually means the user interface and business logic is the same
part.

This is a substantial topic with pros and cons that you need to be aware
of, and googling for 2-tier and 3-tier, "fat client" and "thin client"
might give you better information.

--
Happy Coding!
Morten Wennevik [C# MVP]

[Morten Wennevik]

Re: Architecture question ?

This page seems to be a good entry level for tier information :)

http://www.woodger.ca/archmult.htm

--
Happy Coding!
Morten Wennevik [C# MVP]

[serge calderara]

Re: Architecture question ?

Thnaks for your reply and your post....I will have a look.

Next easy question for you:
what makes the desision to go fora 2 tiers or 3 tiers application if I have
free decision?


"Morten Wennevik" wrote:
[color=blue]
> Hi Serge,
>
> It means instead of having a single executable, you split it into
> parts/layers that communicate with eachother, and may be individually
> upgraded when needed. A 3-tier solution often means, one part is doing
> the User Interaction, displaying and retrieving data to/from the user,
> another part doing the data processing (often called the business logic
> layer) and a third doing database storage and retrieval.
> 2-tier usually means the user interface and business logic is the same
> part.
>
> This is a substantial topic with pros and cons that you need to be aware
> of, and googling for 2-tier and 3-tier, "fat client" and "thin client"
> might give you better information.
>
> --
> Happy Coding!
> Morten Wennevik [C# MVP]
>[/color]

[Morten Wennevik]

Re: Architecture question ?

On Mon, 14 Mar 2005 12:21:07 -0800, serge calderara
<sergecalderara @discussions.mi crosoft.com> wrote:
[color=blue]
> Thnaks for your reply and your post....I will have a look.
>
> Next easy question for you:
> what makes the desision to go fora 2 tiers or 3 tiers application if I
> have
> free decision?
>[/color]

Difficult to say, and google will provide better answers than I can give.
However, one major factor is bandwith. LAN applications that can afford
heavy traffic between Client and Business Logic part compared to internet
applications that needs to be independent for unknown periods.

--
Happy Coding!
Morten Wennevik [C# MVP]