Subject | Re: [IB-Architect] Interbase connection limit and Support relatedProblems |
---|---|
Author | Jason Chapman |
Post date | 2000-07-06T05:45:28Z |
Jason,
I agree this is conventional logic, but why should it need to be this way.
My server is happy, my NW is happy, my WS are happy. Why would I want to
put extra layers of potential failure and debug into the pot. What about
transaction control?
Because of the way this company is growing I intended putting in replication
over n-tier. This way we would have better fault tolerance.
Architecturally - I can't see why 500 users from one box is not feasable.
I need to hear from Ann, Paul, Jim, Charlie about time to fix.
JAC.
I agree this is conventional logic, but why should it need to be this way.
My server is happy, my NW is happy, my WS are happy. Why would I want to
put extra layers of potential failure and debug into the pot. What about
transaction control?
Because of the way this company is growing I intended putting in replication
over n-tier. This way we would have better fault tolerance.
Architecturally - I can't see why 500 users from one box is not feasable.
I need to hear from Ann, Paul, Jim, Charlie about time to fix.
JAC.
----- Original Message -----
From: Jason Wharton <jwharton@...>
To: <IB-Architect@egroups.com>
Sent: 05/07/2000 11:21 PM
Subject: Re: [IB-Architect] Interbase connection limit and Support
relatedProblems
> I think anyone who has a need to support over 200 concurrent connections
> should look into using a multi-tier architecture for their application.
This
> makes it such that multiple computers can pool up 5-10 connections each
> across a high-speed LAN to a high-end machine hosting the database. Thus,
> each middle tier machine can probably host up to about 100-200 clients
> actively working with the database. Products like ASTA and MIDAS are good
> examples but I believe that other ISAPI or JAVA apps would perform a
similar
> function as well. In this way you would be able to load balance the burden
> of so many active clients across an array of machines and funnel their
work
> to the database through pooled connections, no more that 50-100 of them.
> This should fit quite well within the connection limitations of the
> platforms InterBase runs on.
>
> FWIW,
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
> ----- Original Message -----
> From: "Andre Mostert" <amostert@...>
> To: <IB-Architect@egroups.com>
> Sent: Wednesday, July 05, 2000 2:48 PM
> Subject: Re: [IB-Architect] Interbase connection limit and Support
> relatedProblems
>
>
> > We encountered a similar problem on NT. Charlie Caro post a message to
> list
> > a week ago confirming it was the same problem. NT seems to accept the
> > connections above 256, ie the client apps do not get an error, but
neither
> > do the get any response from the server.
> >
> > Regards Andre
> >
> > -----Original Message-----
> > From: Jason Chapman <jason@...>
> > To: IB-Architect@egroups.com <IB-Architect@egroups.com>
> > Date: Wednesday, July 05, 2000 10:43 PM
> > Subject: Re: [IB-Architect] Interbase connection limit and Support
> > relatedProblems
> >
> >
> > What about NT?
> >
> > My largest customer has just blown 256!
> >
> > JAC.
>
>
>
>
> ------------------------------------------------------------------------
> Who invented Gatorade -- and what part did it play in
> winning the1967 Orange Bowl? Find out the true facts at
> http://click.egroups.com/1/6212/6/_/830676/_/962835777/
> ------------------------------------------------------------------------
>
> To unsubscribe from this group, send an email to:
> IB-Architect-unsubscribe@onelist.com
>
>
>