Re: successful migration from client/server to 3 tier systems ?

"Dave Murphy" <dmurphya_at_cix.compulink.co.uk> wrote in article <Dw9z2L.BvA_at_cix.compulink.co.uk>...
> >
> > Lemme see if I can say this without starting The Great 2-Tier vs 3-Tier
> > Definitional Flamefest...
> >
> > From a performance point of view, TPC-C configurations share an
> > important 3-tier characteristic: the distribution of client load across
> > "front end" processors. This is true even though TPC-C doesn't define
 a
> > full 3T logic. For that matter, even some 1-tier (host/mainframe)
> > environments share this offloading characteristic. While they may not
> > be your cup of tea, MVS mainframes scale darn well, thank you very
much!

How does a front-end processor make it 3-tier. Physically there may be only two tiers - the front end and the back end running and between them they can run all of the application for TPC-C. This may give you a "fat client" but, I think, it is still 2-tier. Logically it may be 3-tier but then you can get
logical 3-tier on MVS mainframe also.

> >
> > There is no necessary or general correlation between the number of
> > architectual tiers and delivered performance. IMHO, blanket devotion
 to
> > any of 1T, 2T, or 3T designs not only misses the point, it misses all
> > important points. It's no more sensible than "Blue circles rule! Red
> > triangles stink!"
> >
> > --
> > Jonathan Eunice
> > Analyst, client/SERVER Companion
> Well and sensibly put. Horses for courses basically.
>
> Dave
>
Received on Mon Aug 26 1996 - 00:00:00 CEST